Use Database Initialization Event Listener

[jdpgrailsdev]

Tell us about the problem you're trying to solve

The existing code couples database access with connection initialization. The system wants to gate service startup on database creation and migration. Separating these two concerns will make it easier to adapt the code to an application framework.

Describe the solution you’d like

Utilize the separate database initialization framework created by #12377. This will include replacing calls in the code base to the getAndInitialize() method of the DatabaseInstance /subclasses to simply just return a configured database object instead of also doing the initialization. In addition, each service should create and call the listeners manually on startup before any attempts to access the database is performed. This logic will eventually be automatically called by the application framework.

Acceptance Criteria

• Calls to getAndInitialize() replaced/refactored to return a database object only (do not perform initialization)
• Database initialization occurs as expected for services on startup via manual execution of listeners
• Existing initialize logic removed from DatabaseInstance /subclasses