When switching from an integrable workspace to a non-integrable one,
there was an issue with the top of the instrument widget, with was shown
as an artifact.
When switching from a non-integrable workspace to an integrable one, the
mini-plot didn't expand correctly.

The workspace to be added is no longer necessary, because it appears
that calling afterReplaceHandle only slows the process while not doing
anything noticeable.

This commit thus simplify this, and thus quickens the execution of
replace_workspace by some 30%.

When the workspace is replaced, all of the widgets in the pick tab are
reset to a void status, and the tool comes back to pixel select.

Also, if the workspace is not integrable, the plot is folded.

When the workspace shown in the instrument view is replaced, all the
widgets in the render tab are reset to a fresh state.

The Xintegration widget, which control the integration scroll at the
bottom of the instrument view, should only appear when the workspace
needs it.

This was currently the case, but only if the instrument view was opened
with this workspace : changing the underlying workspace midway, as
intended by replaceWorkspace, was not managed.

Thus, the way the integration range is managed was changed to a more
concise and modular way, so that it is only hidden or shown when needed,
but exists in all cases.

When using replaceWorkspace to replace the workspace being shown in an
instrument window using the python API, the user can specify the
new title of the window.
If none is specified, the name of the new workspace is used.

This adds the C++ function allowing to replace a workspace currently being
shown in the instrument viewer by a new one, and update the view and the
color bar accordingly.

In the instrument viewer, a text at the bottom tells the user how to
interact with shapes (by clicking, dragging etc...), and now also
instructs him how to copy and paste shapes.

Since this becomes the longest text to be printed there, and since it
does not appear at startup, the minimal size of the window has
accordingly to be enlarged, manually this time, so it is not updated
only when the user switches to another tab. This is done by setting the
minimal width of the instrument display widget itself, since it cannot
be set at the layout level.

glViewport takes sizes in device pixels whereas Qt
works in logical pixel sizes. Factor the ratio in for
Qt 5 builds

Clean up calls and increase readability of method names

In the Draw tab of the instrument viewer, when grouping by pixel or
bank, the infotext at the bottom informs the user of what is selected,
so there is at least some info on what is going on.

When picking a single pixel, 2 behaviours are possible : either it's for
masking, and then the picked pixel must be masked on screen immediately,
or it's for picking and then nothing happens to the instrument.
Separating the signals allows for calling the appropriate slot depending
on the current tab.

When not setting an integration scroll bar, instead of just not showing
it, rather not create it at all. This is mmore heavy handed, as it
implies checking for the existence of the object each time it is called,
but it is more reliable (as the non-created object cannot possibly
occupy any space on screen).

This solves the problem of the unclickable Render and Pick tabs.

When saving projects, the save has to register if the instrument window
has an integration scroll bar or not, so when it loaded the loader won't
attempt to add values to a non-existent bar, resulting in a segfault.
Also, it remembers the mask tube and mask pixel buttons being checked
and restores them to their previous state at loading, as for any other button.

When deciding whether or not to show the integration bar, take into
account the possibility of EventWorkspaces or unaligned bins.

This commit adresses the integration scroll bar on the instrument render
tab. A previous commit deleted this bar altogether when it was not
needed, mainly for monochromatic workspaces. But a few methods,
especially in MantidPlot, actually depends upon the attribute being
initialized.

As such, the integration scroll bar object is again initialized in every
case, but a flag "hidden" have been added, which allows it to be created
as a mere shell, without any component that would show onscreen.

In the case of monochromatic workspaces, there is only one bin.
Thus using the integration scroll bar in the instrument render tab
 is nonsensical, and it can be safely removed.

Giovanni Di Siena authored Mar 31, 2020 and Gigg, Martyn Anthony committed Apr 07, 2020

In places other substitutions have been made, e.g
Clang does not yet specialize std::shared_ptr for T[]. Vector
has been used instead. The operator[] methods were incorrectly
marked const but returning a non-const reference - this has been fixed.
Refs #25842

Runs clang-tidy pass by ref across the codebase to fix-up various
warnings we are seeing in cppcheck

Also updated class_maker.py

re #27319

The MPL-colorbar widget resets the limits when for some scale types
and this was disabling autoscaling. This ensures that autoscaling
on the instrument view is only disabled if the values are edited
manually.
Refs #25122