1) MDHistoWorkspace now has a member for the display normalization. This can be set via the constructor.
2) SaveMD saves this bespoke display normalization setting from the mdhistoworkspace
3) LoadMD algorithms look for this setting in the nxs format and will try to apply it to loaded MDHistoWorkspace
4) Added fields to the MDEventWorkspace to accept the normalization to pass on to susequent MDHistoWorkspaces (But not yet writing or reading this in the nxs formats)

Added non-virtual clone() interface with a virtual private doClone()
method to Workspace and derived classes. Workspaces that had a clone()
method before were adapted to have a common interface everywhere. In
cases where there was no clone() method previously we simply throw an
error for now, until this new functionality is implemented.

Some tests/mocks had to be adapted since there there is a pure virtual
doClone() in all abstract classes.

Do to smart pointer incompatibilities (mainly due to old boost versions)
we had do extract the raw pointer from the unique_ptr returned by clone
and put it into a boost::shared_ptr manually, in some cases. See also
issue 12949.

Refs #11209

Currently nothing will compile.
Refs #11209

Since we have put PeakShape in Geometry, SpecialCoordinateSystem must be moved to the Kernel package out of API.

Also start fixing a bug whereby the cluster offsets can become larger than the range of an integer. This has been partially fixed by better calculating the number of possible clusters that could exist. The full fix should be to also change the type of m_id in DisjointElement from int to size_t!

Another issue that is being worked on here is a faster clone of the MDWorkspace. We only care about it's shape, so we just need something the right size to start putting data into!

Add new method on IMDWorkspace to get any special coordinate system settings. On concrete implementations add setters. Add tests for setters and default values.

these warnings have nothing to do with the ticket but the ticket caused large rebuild which let these warnings happens.

and python uncommented

and some code rearrangement.

that had been accidentally hidden by a non-virtual destructor. The MDImplicitFunction was being shared by several objects and deleted several times.

Refs #5319: history in SaveMD and LoadMD.

and started tests

New algorithm can call this with a Composite Implicit function. Responsibility of the algorithm  to generate the CIF correctly from the user inputs.

The framework should be mostly clear of cppcheck errors now.

Because that is more readable