Signed-off-by: Karl Palmen <karl.palmen@stfc.ac.uk>

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.

It is still backwards compatible with the old log-entry format.
Refs #11359

Refs #11359

Unit tested to ensure we are creating a self-consistent peak.
Expose to python and unit test there too.

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

Because json.h is exporting types with dll_export set, which in-turn export types without dll_export set, I have had to disable those specific warnings. We do not have control of this third-party component, so cannot fix the headers.

It is possible( very unlikely) for a peak to be deleted from another thread

Eliminated MantidPlot crash when file is not found.
Eliminated most leading and trailing spaces in text boxes.
Displayed lattice parameter errors

Fixed doxygen warning.

refs #6805
_

Also, more info will now be given based on peak in workspace closes to given peak.

Added menu option to reset default state of all GUI components.
Removed some debug prints.

refs #6901

Run numbers, goniometer readings, hkl values were added if appropriate( only 1 run)
Also, a segmentation fault problem was fixed and failure to give the proper results
for a second PointedAt point was rectified.

This reverts commit 956a6a92.

Lists the contributing detectors for each peak.

Save nexus does not support saving of properties with value of type bool. See PropertyNexus.cpp

instead of ITableWorkspace.h

Follows exactly what's written in the ticket. Peaks in the second
workspace that are within the given Q tolerance in all directions
don't make it into the output.
Note that it's quite possible for a given peak in the first workspace
to be matched to multiple peaks in the second, if the tolerance
is large enough/the peaks are close together.