Allow separate test-modules db

[bradmann]

I'm working on a project where some of the configuration information is stored in the modules db, rather than the content db. In order to unit test this code, it is necessary to have a separate test-modules db, to prevent overwriting the configuration data in the production/dev db.

[dmcassel]

I see config data in the content database more often, but seems like a legit use. I'm thinking we could add a .properties parameter for test-modules-db, which defaults to the app-modules-db. The bootstrap code and the modules-deploy code would both need to take that into account.

[paxtonhare]

Brad's pull request to address this has been merged.