Use the output names struct instead of passing members individually.
Also tidy some broken comment lines

Re #24564

Changed behaviour:

- Minor change to some tests to add Debug flag to ensure that IvsLam outputs that are being checked are actually created. For group workspaces this is currently true anyway at the moment but might not be going forward.

Add new unit tests:

- Check default output names are correct.
- Check that user can override default names.
- Check both with and without debug outputs.

Also fixed ambiguous overload in reflectometry helpers.

Re #24564

Make naming of binned workspace more consistent and remove use of unbinned

Re #24564

Output names are based on the run number. For a group workspace, use the first child workspace's run number

Re #24564

Input workspace history needs to be copied to output workspaces. In
the case of groups, where an output replaces an input, the input history
can disappear before we have time to copy it to the output.
Refs #24372

The pointer to the last workspace should be declared before the for loop
otherwise it will always be a nullptr.

Re #0

The test were performing a multiplication instead of addition/
subtraction.

Re #0

ConjoinXRuns should not care if the workspaces have same bins, only that
they look like blocks.

Re #24462

NumbericAxis::createBinBoundaries and BinEdgeAxis::createBinBoundaries
both do the expected binning correctly.

Re #24492

We should not ask blocksize while other threads might be swapping the
contents of the histograms.

Re #24462

Touches some 'obvious' cases where histograms were misused.

- Replace copies by references to x, y and e histogram data
- Use setSharedX, setSharedY, setSharedE instead of manually copying the
values
- std::move vector data to histograms
- Fix off-by-one errors in SaveReflThreeColumnAsciiTest,
SaveReflCustomAsciiTest, SaveANSTOAsciiTest and ISISEnergyTransfer
- Fix issues in RefAxisTest

Re #24462

Since there are lots of output workspaces declared on the fly, make sure
they are not declared before declaring. The main time this happens is
when the "keep dialog open" box is checked in the algorithm dialog.

Refs #24461

While helping prepare an article, I ended up deriving the equivalence of
delta-d/d = delta-T/T. Since it wasn't a 5-second derivation, it seemed
a good thing to add to the user docs.

Refs #23399