Currently, there is no way to load a CSV file (which is the format
that the full calibration is in) into mantid to be used by the GUI.
Until that is added, the option to select the full calibration has been
hidden from the user.
The functionality is there, so once the loading works for large CSVs the
hide() call can be removed.

The plan for this is to use a separate settings helper to do the work
with QSettings so that multiple areas of the code can access these
functions rather than having it be imported from the model. This keeps
the MVP systems separated from one another.

For thin samples the number of sample elements ends up quite high
and simulating each wavelength is unrealistic.

- Remove repeated searching checks

- Split test into reasonable chunks

- Make rb_num naming consistent

Vanadium output files are now saved to the user directory if an RB
number is specifies so that users can have all of the generated data
from processing.

Focusing now saves as .gss, .nxs, and .dat files.

Now using sample instead of a mix of both of these.

Before, the file finders (MWRunFiles) could only be made read-only,
which did not grey out the text field, just the browse button. This
option has been added and used instead for the file inputs that should
not be used.

Loading the vanadium to be used later on makes more sense to do at this
stage than at the start of the focusing step.

The calibration parameter table that is generated when creating a new
calibration is now loaded back into mantid from the file as a table
workspace, rather then just working in the background.

Parts of the UI that do not do anything are now greyed out to avoid
confusion. The returned values from the load are also added to the new
calibration boxes to show that the load has succeeded.

Loading an existing calibration from the GSAS parameter files now reloads the calibration from the information stored in the file.

This commit adds a catch for if the workspaces or q_lims file have an infinite range

Re #27444

This commit fixes missed line that would allow the index for the max range spectra
to be updated

Re #27444

This commit moves the code for reading the supplies q limits into its own function.
This also fixes a bug that cause an error when trying to read a lim file path that is in
a unicode format.

Re #27444

This commit changes the previously hard coded index for matching spectra to
instead use the workspace with the larges range of x values as these produces the
smoothest match around the edges of the workspaces data.

Re #27444

This commit changes the usage of ConjoinSpectra to a loop using ConjoinWorkspace.
This is done because using ConjoinSpectra the focused workspace can have a
mismatch between specnumbers and index

Re #27444

Removes the Py3Compat shim for Enums and converts all associated callers
to use the natively provided Python version (either through a backport
or in Python 3.4 onwards)

Addresses some issues from a review where:
- A setter is incorrectly named get
- A redundant assignment is removed

Fixes multiple Python 3 compatbility issues where we were encoding into
a byte string, then attempting to use it in the conversion to string

Cleaning up unit tests

Removing a redundant call from one of the tests. And then cleaning up formatting.