Previously an algorithm only appeared when a progress message came in
re #27077

Newer boost bind seems to be causing
compiler warnings on Windows. It's no
longer required now bind is in the STL.
Refs #16578

A user wishes to offset the pulsetime of an event based
on its wavelength so the offset for each event must be
different

It costs slightly more memory but only bytes per workspace
and it is far safer than trying to manage the arrays
properly with new/delete.

The overwhelming use case for this method is to
take ownership of a lattice object into Sample.
Using unique_ptr clarifies that this is happening
at the call site and forces a caller to make copy
if that is truly the desired behaviour. The old code
make a copy internally but this was not obvious
from the method call.

- Adds Python unit test for export
- Adds a `hasAnyMaskedBins` call in the MatrixWorkspace unit tests

re #27319

Refs #26690

Streamed data assumes spectra numbers start at zero.

Main change here is preventing LoadNexusProcessed from running the
instrument save when going via the ESS route.

New problem is that LoadNexusProcessed does not attempt to look for new
Geometry in Nexus as part of the loading, and therefore gives up when it
shouldn't

LoadNexusProcessed also annoyinly looking for group named "instrument",
which we now do not adhere to.

Main change here is preventing LoadNexusProcessed from running the
instrument save when going via the ESS route.

New problem is that LoadNexusProcessed does not attempt to look for new
Geometry in Nexus as part of the loading, and therefore gives up when it
shouldn't

LoadNexusProcessed also annoyinly looking for group named "instrument",
which we now do not adhere to.

There are now options to set if saving History, Instrument, Sample and Logs

No definition provided, so just a link-time error waiting to happen.

Re #26160 merge with previous

This is based on the prototype derived from the meeting at the DMSC last December.

The workflow is as follows:
  - Pool all events received from the Kafka stream into a single buffer
  - When the buffer is to be flushed (i.e. events populated in the EventWorkspace):
    - Parallel sort the event buffer by the detector ID/workspace index
    - Determine group boundaries
    - Parallel insert events into EventWorkspace

Also included is the optimisation of using a spec to ID mapping based on
a vector rather than map.
This provides better performance during the initial event buffering
(where this lookup is made).

Initial benchamrking shows 25M events is a intermediate buffer threshold
for LOKI (9 banks) at 10^7 events per second.
This manages to maintain well over 14Hz pulse rate (with no post
processing).