Mappings should by default never be created but there should be the ability to opt into automatic mapping creation

## Describe the problem
Currently, whenever a module is installed, if the source code would not be put into the default routine DB, mappings are created to force the source code into the default routine DB. While this makes sense when packaging perhaps (in particular when doing database packaging), it doesn't make sense at deployment time if say the user has intentionally set up mappings to another database.

## Describe the solution
The default mode should be to NOT create mappings unless in build mode (once modes are available) but allow opting in with a -map flag (or some other opt in approach).

## Additional context
Related to #658 regarding expanding mappings support to other document types.
Blocked by #633 regarding supporting different install modes.