Jacamar CI v0.25.0

Admin Changes

Introduced Charliecloud run mechanism (!518)
- Details can be found in the Deploying and Using the Charliecloud Run Mechanism guide.
New capability to report build exit code (!562, !570, !561)
- Thanks to changes accepted into the GitLab Runner (MR 5028) it is now possible to report the true build exit code. This means features such as the allow_failure:exit_codes will now function correctly.
- This feature is supported across all executors (with the exception of Cobalt) and only requires that GitLab runner v17.9+ is installed.
- If issues arise with jobs incorrectly identifying the exit code please first attempt enabling the FF_USE_NEW_BASH_EVAL_STRATEGY runner feature flag. If this does not help we encourage you to open an issue.
Optional skip_exit_code_file configuration (!569)
- If unforeseen issue arise with exit code identification if can be disabled via configuration. This will revert Jacamar CI behavior back to using the generic Build Failure.
- ```
[auth]
  skip_exit_code_file = true
```
Added new batch.allowed_actions configuration to limit potential scheduler actions (!567)
- Refer to the Scheduler Actions documentation for the full list of supported actions.
- ```
[batch]
  scheduler_actions = true
  allowed_actions =  ["detach", "cancel"]
```