[FEATURE]: Allow forked repos to override `config` without being impacted by upstream OSS config changes

[liamperritt]

Is there an existing issue for this?

• I have searched the existing issues

Problem statement

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.

Proposed Solution

Add 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.

Additional Context

I've previously spoken with @rederik76 and @PremRajendran about this problem and proposed solution.