Modify MATS code to point to 'development' scope

[gopa-noaa]

Currently data is on collections under the _default scope. Code and probably externalized configurations needs to change to point from _default to 'development scope. The externalized configuration should only go down as far as bucket and scope, NOT to collection level, since application code will need to access data from multiple collections under a scope, specifically because we now have a 'COMMON' collection, that would also be pertinent to the application.

[mollybsmith-noaa]

@gopa-noaa The scope change is for all queries and connections within MATS? And I think we'd probably still specify (multiple) collections in the external configuration like we do for mysql, it's much easier to change there than if it's hardcoded in the app. Thanks for the heads up though, I'll get that adjusted.

[gopa-noaa]

@mollybsmith-noaa
MATS and middleware can probably can still use external configuration for scope and collection.
There would be the new "COMMON" collection , but what would end up there is still kind of up in the air.
We have to wait until data is copied to scope "development" , collection "METAR" before we can test this.
The plan is to have the data exist in both places until we test and certify all apps before the original _default scope os dropped. I will work with you on the MATS app and middleware transition.

[gopa-noaa]

This issue is blocked by:
NOAA-GSL/VxIngest#396

[github-actions]

This issue is stale because it has been open 90 days with no activity.