Add a DXL parameter to open baselines with the standard view instead of the default view - similar to (current version) modules - to better control outdated dynamic content calculations

Modules can have views. A view can be set to be the default view for a module. A default view gets opened by default, when the module is opened.
The standard view is a view that contains the object ID and Object Heading+Object Text columns, no filters, no layout DXL, no attribute DXL. It is the lowest common denominator of (calculations) complexity that all modules have in common. The standard view can be set as the default view. The standard view is the default view, where no other views exist.

Baselines are modules frozen at a specific point in time. Baselines cannot be modified. Baselines have their default view frozen with them at the time of creating the baseline. The default view can contain filters and layout/attribute DXL that can become invalid as the (current version) module changes. Baselines open with their default view, where one is set at the time of creation. This cannot be changed later.

DXL allows to open a module with 
- a specific view
- the default view
- the standard view

DXL allows to open a baseline(d module) with
- the default view

ONLY.

This can lead to problems where the default view of a baseline contains DXL in filters, triggers, attributes or layout columns; that is ideally correct at the time of creating the baseline, but may fall out of currency over time as the main module evolves. Adding a level of control to opening the baseline without custom DXL firing, would greatly improve predictability of behaviour, and specifically avoid a client crash, where baselined DXL is incompatible with batch-mode DXL processing.