Region configuration kept separate to pipeline code

[MichaelHanksSF]

The aim here is to keep region-specific configuration instructions out of the main codebase. The benefits of this are:

• [ ] Pipeline code is blind to the region-specific instructions - it just loads the config it is told to and uses these
• [ ] Customer data (in terms of processing instructions) are kept separate

We could do this by having the config jsons kept in a separate, private repository, which is then called on by the main code.

Alternatively, we could manage this by a database which could be interacted with directly by the regional hub users.

[MichaelHanksSF]

0.5-1 day