- Add a new property, ThetaInLogName, to ReflectometryReductionOneAuto, which is used to find ThetaIn from the given log value.
- Note that if the ThetaIn property is also specified, that will take precedence.
- Add another new property, CorrectDetectors, to make it optional whether detectors are moved to ThetaIn (whether specified via ThetaIn or ThetaInLogValue). The default is true to maintain the previous behaviour when using ThetaIn.
- Pass through the overridden ThetaIn value to ReflectometryReductionOne. If ThetaIn is not specified, theta is calculated using SpecularReflectionCalculateTheta, and this is also now passed through for consistency. The latter does not work for some IDF setups but in those cases ThetaIn should be overridden with one of the above properties (and this no longer needs to affect the detector positions if CorrectDetectors is set to false).
- Disable the DetectorCorrectionType drop-down if CorrectDetectors is false.
- Disable the ReductionType drop-down if SummationType is SumInLambda.
- Improve an error message to report angles in degrees rather than radians.

Re #20397

Re #20120

Add a Diagnostics property to the RRO algorithm (exposed in RROA) which
outputs intermediate workspaces to the ADS.

Re #20123

Pass ThetaIn through from ReflectometryReductionOneAuto to
ReflectometryReductionOne, instead of theta0 (which is different in the
divergent-beam and non-flat-sample cases).

This reverts commit 188007ef.

- Remove the temporary theta0 from RROA
- Pass ThetaIn from RROA through as theta0 in RRO
- If theta0 is not provided in RRO, use stheta from the logs instead

- Add a new property to determine the type of summation
- Move the new properties to the base class
- Add validation

Still output IvsQ_unbinned even if the rebin and scale step fails; log
an error instead.

It does not make sense to integrate monitors when a correction algorithm is used