Introduce $binary evaluate ... --run-id-starts-at $integer as option to start the "run ID" from something other than "1"

[zimmski]

Please help us keep the number of duplicated issues small. We kindly ask you to add your input to the appropriate issue or PR in case your feature idea is already being tracked.

• I have searched the existing feature requests, latest roadmap and open pull requests.

Problem

When we split up an evaluation in our CI and let multiple CI jobs use the "--run 1" option, we only receive "1" as run IDs.

Solution (optional)

Tasks:

• Simplify how runs are created for all our code. It seems that this is right now all over the place.
• Introduce --run-id-starts-at $integer as option to start the run ID from something else than 1. Must be >0.

A scenario like $binary --runs 5 --run-id-starts-at 3 should then produce 3 4 5 6 7 as IDs.

[bauersimon]

seems to be fixed through a8995ec