Run numbers for local runs

Description

Keeping track of local runs is tricky at the moment. No run number is assigned (i.e. run 0) which leads to files being overwritten. Additionally, the scans that do not require a run are not even using the run folder.

Implementing a robust run numbering scheme would significantly help operations.

Possible fixes

1. Add a configuration option to the GEMApplication specifying whether the run number is locally/globally assigned
2. Forward this information from the GEMSupervisor to the managed applications
3. Build a run name with the above information, e.g. G000123456 or L4212258945. It may also contain the run type.
4. Create a local run number if the run number is to be locally assigned. A typical numbering can be YYYYMMDDMMSSXX if that would work with the TCDS application. Edit: a run number of 0 can be sent to the TCDS. The return of the std::filesystem::create_directories function can be used to check for uniqueness.
5. Ensure the whole code uses the functions developed above. The treatment of the non-calibration scans is not obvious at the moment due to the separation between the GEMSupervisor and the Calibration applications.
6. Present the current run number to the user (in the GEMSupervisor web application?)