Simplify interface to database module

[lorenyu]

Ticket

Resolves navapbc/template-infra#752
Contributes to navapbc/template-infra#726

Changes

• Reduce the number of configurable parameters to the database module by:
  • Reorganizing /infra/modules/database to be a folder of two modules, a "resources" module and a "data" module
  • Move the current database module to be the "resources" module
  • Move all database-related data sources in the service later to be the "data" module
  • Move most database-related parameters in app-config to an internal "interface" module that root modules don't need to know about

Benefits of this approach is that it:

• Simplifies app-config to only configurations that are intended to be updated by the project vs configurations that are only there to facilitate dependencies between root module
• Encapsulates the data sources in the service layer's root module
• Simplifies the creation of the database itself in the database root module

Context for reviewers

See description in changes, but this is a new architectural design I've been discussing with @rocketnova last year that was born out of an idea by @sonicos . I think it solves a couple of problems at once. In addition to simplifying data source access it also helps address the problem stated in navapbc/template-infra#726.

This is purely a refactor PR, there are no functional changes.

Testing

Running make infra-update-app-database APP_NAME=app ENVIRONMENT=dev only no diff except for a last_modified timestamp on a file due to moving the database module from /modules/database to /modules/database/resources

Running make infra-update-app-service shows no changes

Preview environment

♻️ Environment destroyed ♻️

[lorenyu]

Done in navapbc/template-infra#841