BREAKING CHANGE:

Allow forked repos to override framework config without being impacted by upstream OSS config changes.

If a forked repo makes changes to the src/config folder to customise the framework for their purposes, upstream OSS changes to the files in the src/config folder risk impacting downstream forked repos.

This change moves the framework config from src/config to a new src/config/default folder (BREAKING CHANGE), and adds an empty src/config/override folder where forked repos can add and change framework config without any risk of upstream OSS config changes impacting their customised config.

The proposal is that if there are any non-hidden files within src/config/override, then this folder is leveraged by the framework for configuration. Otherwise, the framework will fall back to src/config/default.

This has been manually tested against the sample job "Run 1 - Load and Schema Initialization":

• Test without src/config/override: https://e2-demo-field-eng.cloud.databricks.com/jobs/314656373533508/runs/1013669694316232?o=1444828305810485 (failure on feature_samples_pipeline_table_migration is unrelated to this change)
• Test with src/config/override, overriding format -> yaml: https://e2-demo-field-eng.cloud.databricks.com/jobs/314656373533508/runs/315303244749666?o=1444828305810485
• Test with src/config/override, but missing global config: https://e2-demo-field-eng.cloud.databricks.com/jobs/314656373533508/runs/753936030023929?o=1444828305810485
• Test with config in src/config instead of src/config/default: https://e2-demo-field-eng.cloud.databricks.com/jobs/314656373533508/runs/1077812474226905?o=1444828305810485

And here's the test for "Run 2 - Load":

• Test without src/config/override: https://e2-demo-field-eng.cloud.databricks.com/jobs/630815393479142/runs/215754468960491?o=1444828305810485 (failure on feature_samples_pipeline_table_migration is unrelated to this change)