re #28093

This commit removes header guards from tcc files that was missed in search script

This commit replaces #endif statements mistakenly removed by the automatic pragma once replacement

Signed-off-by: Harriet Brown <harriet.brown@stfc.ac.uk>

This commit replaces all header guards in API with #pragma once

Updates the IndexType to have a new method to convert to a string, this
reduction in strict type safety could mean developers could abuse
SpectrumIndex -> String conversions. However, it enables us to print a
string representation of an index, such as if we need to say index x is
out of range.

Previously, the at() access on the IndexProperty map would throw with an
invalid key message. This is useless for anyone who is trying to Mask a
range of specra (such as 500), as you have to guess if the min / max or
a middle value was bad.

The old behavior is that newer cmake did not use the variable in the
source files because it is unset.

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

This was due to:
1. Too long a default UpdateEvery default
2. Too infrequest progress updates from MonitorLiveData
3. The Algorithm Details box not adding an algorithm until it sends a progress update
4. The StartLiveData custom Dialog not showing the default for UpdateEvery

Fixes:
1. Decreased the default UpdateEvery from 60 to 30 seconds
2. Change the default timeout for FakeISISHistongramDAE from 30 to 60s
3. improved the progress logging for MonitorLivedata to update more frequently with an idle counter as well.
4. Changed the tie function used in custom algorithm dialogs to set the placeholder text for line edits
5. Changed the log level for user cancelling of algorithms from Error to warning so it does not trigger the notification service
6. Changed the log message for user cancellation from Terminated to cancelled to reduce confusion

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

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.