Make the settings path configurable

[mjkanji]

Is your feature request related to a problem? Please describe.
I often use custom values for things like the destinations for sources, property files, etc., and just discovered the docs on .dbt_coves/config.yml, which lets you define defaults for the various options, so I don't have to keep passing these values via the CLI.

However, I'd rather not add another folder to my project root and I prefer keeping all config in a config/ directory.

Describe the solution you'd like
Make the path of the config.yml configurable. Ideally, this could be via an environment variable.

Describe alternatives you've considered
N/A

Additional context
N/A

[jim256]

@mjkanji,
Like you, I want to keep my dbt project focused on just dbt-core itself, and I have a parent directory that has a lot of things like dbt-coves, dbt-osmosis, pre-commit configs, etc.

FWIW, the CLI provides --project-dir PROJECT_DIR, which is described as:
"Which directory to look in for the dbt_project.yml file. Default is the current working directory and its parents."
I use this to have all my configs, CI/CD, etc. objects in the parent directory.

There's also --config-path CONFIG_PATH, which is described as:
"Full path to .dbt_coves.yml file if not using default. Default is current working directory."