Removes all of the from __future__ imports that open and close the
brackets on the same line. This is most of them.

Also updated class_maker.py

Attempts to flush out the cause for the failing nightly clean build on
Windows. This is periodically failing on both the release / master clean
builds without any reason why.

Fixes all flake8 3.7.9 warnings as part of the Python 2->3 transition.

The stdDev function that was deleted in this branch often returns different values  than the 'correct' value which is sqrt(eigenvalue)  - which is now used. Typically the difference is  <0.5%, however occasionally the stdDev function returned a std deviation that is unrealistically small (by two orders of magnitude), this behavior is not as yet understood, but since the function is no longer used it is appropriate to change the test values.

This commit updates the reference files for tests where the transmission
workspace is output from ReflectometryReductionOne. The refactored code
in this PR has introduced a fix in this algorithm to output the
transmission workspace after it has been rebinned to detectors.
Previously it was output before the rebin step, hence the minor
differences in the output. Note however that the final results of the
reduction (IvsQ workspaces) are unchanged.

This commit also moves the code to set the output workspace to the
bottom of the function that does the transmission correction, to help
avoid a similar problem happening again.

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

System tests for Abins are modified to calculate up to second-order
excitations only (as third and fourth-order are currently disabled.)

In addition, the test data for two other tests needs updating;
BezeneBinWidthCASTEP and TolueneScale have small changes in the
results. This is associated with a more conservative criterion for
discarding small values compared to the previous system; results
similar to the previous setup can be obtained by modifying the
threshold used in
SPowderSemiEmpiricalCalculator._calculate_s_over_threshold

Removes Python 3 only code (to comments where possible) since the next
release must be Python 2/3 Compatible

This commit adds system tests for the new fourier filter in powder polaris.

re: 27773

Adapt the command interface and user file parser to use sans state
objects, instead of the new containers (which duplicated the data
objects).

This is a large PR as we must change all call sites, partially unlink
the reading of run data (the dict converter still takes data info which
needs fixing), and create classes that facade the building process

As the state folder was starting to fill I also took this chance to move
them into their own package, so we have a seperation of data and impl

This commit adds system tests for the new fourier filter in powder polaris.

re: 27773

A new boolean parameter SimulateTracksForEachWavelength has been added to
the MonteCarloAbsorption algorithm. This exposes a switch on the MCAbsorptionStrategy
that was present before this change but was hardcoded to False.

The parameter NumberOfWavelengthPoints is only required if SimulateTracksForEachWavelength
is set to True. This change means that an attenuation factor is calculated for all wavelength
bins if SimulateTracksForEachWavelength=false. To facilitate this a performance enhancement
has been made to the Material class to calculate the total scatter cross section and the
absorption cross section once when the Material rather than every time these cross sections
are retrieved by the MonteCarloAbsorption calculation.

This change required some unit and system tests to be updated eg ILLDirectGeometryReductionTest
has been changed to remove the NumberOfWavelengthPoints parameter and the reference file to be
updated. To make this test more robust I have increased the number of scenarios used in the MC
simulation from 5000 to 20000

Also required updates to system test files. Updates to complexShapeAbsorptionsTest
include changes to increase number of scenarios and increase of tolerance so tests
are more robust to changes in random number sequences in MC simulation

A PeaksWorkspace is now iterable and no longer responds to
the table lookup api.
Refs #26839

I have deleted the MultiPartEnvironmentOverlap test because it wasn't being run
due to the parent class being SampleShapeBase instead of SampleEnvironment.
The test MultiPartEnvironmentTranslate already tests overlapping environment
components with a +/- 2.5 offset on two components based on cube.stl (cube.stl
is a 10 x 10 x 30 cuboid) so didn't seem benefit in fixing the xxxOverlap test

A switch has been added to the MCAbsorptionStrategy class that allows a pair
of before scatter\after scatter tracks to be used to calculate the attenuation
for a range of different lambda values. This will improve the speed of the Monte
Carlo calculation. The Monte Carlo calculation currently sets the switch to
reuse the tracks without exposing this in the algorithm parameters - I've mainly
left the "old" approach in place in case any further wavelength dependent effects
are added to the absorption calculation eg beam spreading

In order to add the reuse while retaining the original behaviour (via the switch),
I had to reverse the order of the event and lambda loops. The previous code looped
over lambda with an inner loop of events. The event loop is now the outer loop, so
even with the switch set to not reuse tracks the results will change slightly if
the simulation isn't converged

The function MCInteractionVolume::calculateAbsorption has been split into two:
- track generated done in calculateBeforeAfterTrack
- absorption calculation done in calculateAbsorption

The relevant unit and system tests have been adjusted. In particular the tests in
MCInteractionVolumeTest have been split out so the track generation and absorption
calculation are tested separately

Refs #27744

Refs #27744