Re #9543. Correct indentation.
Re #9543. Handle the addition of monitor workspace chunks.

This step explicitly adds monitor workspaces in addition to the main
data. This means that if the monitor workspace is still present after
the processing step (a user could extract it there if they wanted), it
will be available for the post-processing or be carried right through
to the output if there is no post-processing step.
Re #9543. Don't retain the accumulation workspace at run end.

I don't see why there is any need to keep a copy of this around if
renaming at end of run. Just keep the principal output workspace.
Re #9543. Ensure the monitor workspace is kept at end of run.

If 'renaming' the run at the end is chosen, the Clone algorithm is
run - override the default loss of the monitor workspace in this
algorithm by pulling it out and cloning it as well (and then putting
it back in).
Re #9543. Clear Coverity warning.

Tangentially related to the work of the current ticket.
Re #9543. Remove unused variable.
Re #9543. Remove unused variable.
Re #9543. Make sure monitor WS is kept if not preserving events.

Also add tests for this.

There's a call to ConvertToMatrixWorkspace if the option to preserve
events is off in a live data run. This propagates any monitor workspace
through this algorithm, though note that in the case of the SNS listener
at least a Rebin or something needs to be performed on the monitor
workspace to set the X boundaries.
Re #9543. Add an option to not clear the monitor workspace pointer.

This is particularly required to be able to use this algorithm in the
post-processing step of a live data run. Unless this new property is
set to false, things fail on the second time around because the monitor
workspace has been cleared out of the accumulation workspace.
Merge remote-tracking branch 'origin/feature/9543_accumulate_monitor_data_in_loadlivedata'