Read-only database config rough spec

[goldpbear]

NOTE: This is a rough outline of a tech spec for a read-only database config. Not final.

As we prepare to support a GUI for editing Mapseed maps, the first step will be to transition our config.yml properties to database tables and read from this source when hydrating our components.

Goals

• Cleanly separate config values from the static bundle build. The intention is to have core code bundles that fetch their config properties at run time.
• Move all config properties to database tables behind the Mapseed API.
• Build out endpoint(s) to read from these tables.

Non-goals

• i18n will not be fully supported initially. It will still be possible to localize database-driven bundles, but the necessary locale files will need to be created manually.
• Writing config values is not a goal at this stage.