The unit test that existed before used a mock of mantid
and of a table workspace to test. It is better practice to
avoid mocking when possible, and this way the internal implementation
of the unit test can change whilst maintaining the validity of
the test.

Started work to make analysis routine into an object.
Created folder to keep my work organised.

Most of the work consisted in including 'self' in functions and
replace the previous 'ic' methods with 'self' methods

The first part of the routine up until the MS and Gamma corrections
is now working, have not tested it yet.

Fixed second part of routine to use analysis object.
Currently running in its entirety but have not checked tests

Added a system test for the new AnalysisReduction object.
All system tests are passing. The system tests have a coverage of
95% of analysis_reduction.py and are very stringent, so it is
fairly safe to say that this transition to OOP has not introduced
any new bugs.

Instead of fit the workspace in one go, and then create a
table and the final workspaces, it makes more sense to populate the
table and the final worksapaces row by row as the spectra are being
fit row by row.

- Renamed functions
- Changed functions to use self._row_being_fit instead
of using the row as a function argument
- Deleted functions made redundant due to previous commit

When the input workspace contains columns of zeros,
these should be replaced by the fitted profile before
doing the multiple scattering and gamma correction.

Made it easier to read and understand what the routine
is doing when calculating the mean widths and intensity ratios.
Put the multiple scattering and gamma corrections into its
own function.

This work changes analysis_routines.py to be the "glue" between
current interface and new oop interface.

The idea is to keep the current interface for now and focus on
turning the analysis rouinte into a Mantid algorithm.

The analysis system tests were changed to account for this re-routing.

Rewrote routine for chaining two analysis routines together,
known as the 'JOINT' procedure.
This means that the resulting means and intensities from one
analysis routine, usually backscattering, are used as the starting
guesses for forward routine, and all widths except the lightest
element (usually Hydrogen) are fixed.

New procedure using the AnalysisReduction object is easier to read and less prone to bugs.

Also checked that figures and result files are saved at correct
location.

The new AanalysisReduction class is already being tested by
test_analysis.py so the removed test was redundant.

Updated procedure to estimate H ratio to use new object of
AnalysisReduction. The ratio is set to always be in relation to
the lowest mass in the sample.

I added two functions to handle constraints with the new OOP
interface, but promptly forgot that they are not necessary in
the current interface as it is, so I commented them out for now,
to be used in the future when the shift towards using the new
interface happens

Made imports clearer, deleted useless comments and organized some
sections into separate functions.

This commit finalizes the transition between the previous
analysis routine using only functions and the new one using an
object to run the routine. All of the intermediate files have
been deleted and final routine was renamed to the existing
analysis_reduction.py

Separated import statements by three groups of standard library,
external imports and mvesuvio package imports

Implemented review suggestions

Uncomment functions to use in the future