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

We use the sets for each presenter to calculate the difference. If the difference between the peaks workspace is the same as the original set, then there is no overlap, and we may accept that presenter.

A number of unit tests have been introduced to verify this.

New tests to cover this changed functionality.

This allows the PeakTransform to be used in multiple projects. It is required in Crystal where Peak coordinates must also be properly selected and transformed according to an IMDWorkspace setup.

Refs #9059

Color is more consistent in the python API. Since this interface is being exposed via SIP. It makes sense to rename the colour functions.

Zoom to a peak of a specific peaks presenter and select the corresponding row in the mini peaks workspace.

This is associated with a fix in what thread the code is executed upon. There is a Hack (marked HACK) in one of the presenters that will need fixing yet.

Selected aspects can be controlled both from the GUI and via python. Tests will need reworking.

I have also exposed peaks presenters via python. Seems to work ok thus far.

Additional work required to PeakTransform, PeakBoundingBox and PeakTransform to get this to work.

This has been somewhat rammed in.

However, its not worth a clean implementation here unless we know that the effort will be worth it.

Handle the case that the mdworkspace does not appear self-consistent. Also handle the case where an integrated peaks workspace is being viewed in a coordinate system that is not the same as the one it was integrated in.

Added components to all tiers to support this functionality. Have also extended the tests to cover the new functionality.

.The last set of changes allowed zooming, but now we should be able to land on the correct slice location too.

Toggle between hiding and showing the peaks workspaces.

For future work we need to get access to the peaks workspaces (const).

Redesign so that the ConcretePeaksPresenter uses a different PeakOverlayViewFactory if the PeaksWorkspace has not been integrated. This used to just throw in the past.

Will still need a mechanism to select the factory. PeakTransformSelector will do this.

I havent done any benchmarking, but there are functions being run that dont always need to get run. Ive cached some variables rather than recalculate the results too. Would have been better to benchmark first, but Ill do some proper optimisation under another ticket at a later date.

Do not allow the user to have access to these features unless everything has been setup properly.

Fix issue where peaks dont display until slider is moved.
Fix issue where the correct slider to use is unknown.
Fix issue where the peakstransform is not getting updated with the new plot axis
Fix issue where the peak shape is fixed circular based on one axis range.