Shift the first orbit along with the ITS ramp-up start of run

[sawenzel]

This fixes a problem in the ITS ramp-up anchoring shift and adds a unit test.

• The shift moved --sor and --timestamp but left --first-orbit at the orbit of start-of-run, while the timeframes a job simulates are placed by orbit.
• A job at production offset 0 therefore still sampled the first orbit of the run, where ITS/Calib/TimeDeadMap masks all 24120 chips, and wrote no ITS digits at all: no ITS tracks, no reconstructed collisions, and an AOD whose collision table is empty.
• HBFUtils.startTime and HBFUtils.orbitFirst also disagreed by the ramp-up duration.
• Both coordinates now move together in shift_anchor_past_ITS_rampup.
• For run 571781 with SPLITID=1 the first orbit moves from 20505888 to 20562116, past the 34080 orbits that run's dead map masks.

https://its.cern.ch/jira/browse/O2-6565
https://its.cern.ch/jira/browse/O2-6894

[github-actions]

REQUEST FOR PRODUCTION RELEASES:
To request your PR to be included in production software, please add the corresponding labels called "async-" to your PR. Add the labels directly (if you have the permissions) or add a comment of the form (note that labels are separated by a ",")

+async-label <label1>, <label2>, !<label3> ...

This will add <label1> and <label2> and removes <label3>.

The following labels are available
async-2023-pbpb-apass4
async-2023-pp-apass4
async-2024-pp-apass1
async-2022-pp-apass7
async-2024-pp-cpass0
async-2024-PbPb-apass1
async-2024-ppRef-apass1
async-2024-PbPb-apass2
async-2023-PbPb-apass5