Support different modes for build and deployment

Per conversations with HS, we'd like a way to differentiate between installation during build-time (i.e. loading a module in order to package and maybe publish it) vs. deployment-time (i.e. installing a pre-packaged module on an instance).

Example use case:
Certain module configuration should only be performed at deployment time. It may be specified in CPF files or in a class that is in an element in the module.xml. This could include ObjectScript code that should be run before/after an existing lifecycle phase. Many of the same lifecycle phases are run as part of publication and straight installation.

Some ideas from @isc-kiyer: IPM could add this functionality to the Invoke argument, Scope (currently can be empty, test or verify), and change it to a comma-separated list which could include the mode and perhaps custom values. Alternatively, IPM could create a different Invoke argument, CustomScope, paralleling the CustomPhase argument.