This commit makes sure all widgets' invalid/valid state is updated when resetting to defaults

Re #23051

Re #23051

This just ties up the existing button with the recent functionality to get defaults from the algorithm/parameters file.

Re #23051

Get the new defaults and update the model, then update the view, when the instrument has changed.

Re #23051

- Move the boost optional defaults file to API so it can be accessed outside MantidAlgorithms
- Replace the unused InstrumentOptionDefaults struct with a class that uses the boost optional defaults file to get default values from the algorithm or instrument

Re #23501

MainWindow and Batch subdirectories have been created for these GUI components.
A Common subdirectory has been created for miscellaneous shared utilities.
Unused files have been removed

- Notifications are sent from tabs up to the Batch and then back down to the Runs Table
- The runs table will need to handle this and reset the processed state the in reduction jobs (not implemented yet)
- Tidy up some naming of the instrument notification functions

Re #23041

Disable widgets when autoreduction is in progress.
Fix a bug where the Experiment settings grid was not disabling its child widgets - they need to be disabled individually.

Re #23041

Re #23041

Add MVP model for flood corrections to the experiment presenter's model and add flags for debug and include-partial-bins options

Re #23043

Manually re-add recent gui additions from master that were not merged because of the file restructuring:
- flood correction inputs
- debug check box
- include-partial-bins check box

Re #23043

Re #22263

Re #22263

Add unit tests for all combinations of start/end being set/unset and valid/invalid

Re #22263

This uses zero as a special value to mean unset. The range can be checked to see if it's valid depending on whether both or none must be set together. This is true for the background range, but the other ranges can have min/max set independently.

Re #22263

Re #22263

Re #22263

Re #22263

Re #22263

The range is not set in the model if the user enters invalid values

Re #22263

Stitch params are now validated immediately rather than alongside the per-theta defaults

Re #22263

Re #22263

Re #22263

Re #22263

This assumes that the value always exists, which it will once pre-populated models are injected into the constructors

Re #22263

Also tidied file layouts to be more consistent.

Re #22263

Re #22263

Re #22263

- Tidied up some of the validation, moved some of the logic out of the
Experiment Presenter and into a new table validator class.
- Generalized RowValidationResult into ValidationResult.

Re #22263

Re #2263

Re #22263

- Prevented warning dialog for non-unique angles from showing when
  not modifying the angles. The red highlighting remains.
- Moved additional classes out of Experiment presenter and split some
  of the validation up into smaller functions

Re #22263

Re #22263

Re #22263

Re #22263