Added support for persistent databases between program runs

These modifications support the persistence of the database configurations between runs. In the "dev" profile, the database is created, prepopulated, and destroyed for each program invocation. This is essential to create a known state for unit and regression tests. However, for an actual installation, the databases need to be persistent.

This set of commits allows the created, prepopulated, and destroyed database features to be selectable on a per-profile basis. Additionally, the business-config.xml files for DC and TP are normalized to be as similar as possible for future maintenance.