Add support for performing module-specified namespace or system configuration at installation/load time

[isc-eneil]

Per conversations with HSOPS, we'd like to ask for support of pre-packaged installation-time configuration of a module as part of the install/load command (or another command that also encompasses installation/loading). In particular, we imagine modules that contain a CPF file that is identified either by its name or file path would be iris merged programmatically before the Reload lifecycle phase.

This feature would not include user-specific installation-time configuration. That is a separate issue.

[isc-tleavitt]

Spec:
You can put a CPF file path in module.xml as a resource (you can have more than one)
We'll add a pre-reload lifecycle phase (named "Initialize") and hook into that from the CPF file's resource processor class - default behavior is to do the CPF merge during Initialize, but a resource attribute can be overridden to do this later instead (in a named phase)

Sets of configuration:
Creating namespace + database(s) into which module will be installed (covered in #629 which becomes a non-issue if we drive from CPF merge rather than IPM as a starting point, which we will do via a sample file in docs)
Module-specific configuration (mappings, creating roles/resources, granting SQL privileges - covered here)
User-specified configuration (OAuth config, UM integration config - equivalent to an "env" file for docker run; this is covered in #632)

Orchestrate this across multiple namespaces: #630 - also goes away with "CPF merge drives everything"