This Commit fixes a bug in in the mantid plotting in workbench where if a MDHistoWorkspace, or any workbench without an `isDistribution()` method, was plotted users would not be able to open the context menu as it would encounter an error when tying to work out if it is possible to normalize the plot.

re: #28082

Change the SANS Beam Centre Finder to prints the average residual change
between two quarters. This allows for direct comparisons, previously if
a user increased the radius limit it would appear to perform worse,
despite actually doing better. This was because the additional number of
points was not accounted for.

This implementation is based on the implementation in MantidPlot.
A C++-based executor has been added that can execute Python code
with the option of installing a trace function to update
a progress marker on a given editor window.

The old implementation attempted to chunk up the script into
the smallest executable blocks and mark each of these as when
they were executed. There were 2 issues:
  - the chunking of the scripts was error prone as it actually
    requires a good knowledge of how Python internally handles
    indentation etc. It was fairly easy to break and future
    internal updates to Python would have required unknown changes.
  - the progress reporting resolution was far poorer than MantidPlot
    as the actual line being executed was not reported but inferred
    by what block was being executed giving a false sense of progress
    through a script.

Re #27633

Re #27633

When assigning to a list of outputs when calling the algorithm in
python, the outputs must be specified in the order they are declared,
even if they are optional outputs like IvsLam. This means that if we
want to specify the transmission workspace output we must first specify
IvsLam even if debug is false. Some of the algorithms always output
IvsLam if the name was given whereas others did not. They now always
output it if the name is given.

Note that this means you may now get an error if you don't supply enough
arguments whereas previously it was ok. It is ok if you just specify the
IvsQ output(s) but beyond that we do not know whether the output should
be IvsLam or the transmission, so we require all of them, hence the
error. This is better than it assigning an unexpected output so I think
is ok, and is the only way I can think to do this.

Re #27633

In workbench normalisation was being set to true in the fitting algorithm for distribution workspaces leading to incorrect output parameters.

This commit removes unnecessary comments in SaveRMCProfile and SavePDFGui docs

Re: #27774

Updates surrounding docs to reflect the new API name and tidies the
example import up

In a previous commit I added we treated 0. offset as a special case of
doing nothing, as naively I assumed the IDF position of M5 is correct

However, this skips the logic which repositions the monitor at the rear
detector, then applies a shift. So a shift in rear-detector relative to
the monitor IDF position would result in a different result.

This lead to confusing behaviour and incorrect results when a shift of 0
is set.

Updates the SANS Release Notes to include all the various fixed issues
falling out of the tab fixing work

Fixes an API call to plotfunctions.plot(..., LogName=""), to
axesfunctions.plot(..., LogName) which resolves the issue

When doing an error bar plot of a workspace which has the distribution flag set to true it will be treated as normalised so when a curve is overplotted onto the figure it will be normalised.