81 config access

[aradhakrishnanGFDL]

addresses #81
Also includes updated CI tests
https://github.com/NOAA-GFDL/CatalogBuilder/actions/runs/13401440551

[aradhakrishnanGFDL]

Test instructions:

gen_intake_gfdl.py /archive/am5/am5/am5f3b1r0/c96L65_am5f3b1r0_pdclim1850F/gfdl.ncrc5-deploy-prod-openmp/pp test0211_1

catalog generated here /home/a1r/github/fork/forkCatalogBuilder-/catalogbuilder/scripts/test0211_1.json

opened data and tested a bit with /home/a1r/github/fork/forkCatalogBuilder-/catalogbuilder/scripts/getdatasets.py

Also tested this python script due to some renaming being done to config files:
gen_intake_gfdl_runner_config.py (main repo)

Updated CI tests to run the default mode with a local conda install. Suggest running a stand alone test with the catalogbuilder installed as a conda package and with the new entrypoint changes from another PR, once both PRs are merged in unless there is an easier way to test both from conda, if one has the time to do a local install.

[aradhakrishnanGFDL]

These [CI tests]

(https://github.com/aradhakrishnanGFDL/forkCatalogBuilder-/actions/runs/10269451721/workflow#L37-L45) ensure that the default option without passing the --config works. It uses this
default configuration: https://github.com/aradhakrishnanGFDL/forkCatalogBuilder-/blob/81-config-access/catalogbuilder/scripts/configs/config_default.yaml

--config also works as expected based on CI tests.

A user that does not want to use the default config has two options:

1- In their local repository, replace the config_default.yaml with what they want (e.g. add column long_name)
or
2- Simply use the --config.

For [1], this can't be used with fre-cli way of running things unless there is a feature being requested.