Improve initial default ADM load process

[DavidEdell]

The startup sequence currently detects a first-time initialization and loads the default ADMs into the database. On occasion, this process appears to fail due to either timing, or a partial re-initialization of the containers.

To improve reliability and simplify the startup sequence I suggest that we:

• Remove/deprecate the first-time startup logic
• Use existing tools or DB instance to load the standard suite of ADM schemas and export data to a SQL file(s) to be added to the schema definition
• Note: Data SQL files should be the last files to be parsed, and INSERTs should be internally ordered to avoid foreign key conflicts without temporarily disabling said checks. Most tools do not automatically account for dependent keys while exporting.