[WIP] Enable Initializing Second Experiment From Library

[michaelmckinsey1]

Description

• Depends on Automatically Enumerate Dryruns and MpiOnlyExperiment #904
• Issue described in Cannot initialize second experiment from library #932
• This can be worked around by running the pytests individually, but this complicates the code coverage.
  • Example of error code checking on command line tests here https://github.com/LLNL/benchpark/pull/982/files#diff-a3ddd7238fc6e36daeb0ef76e93fe15cc87824bd3299888075210c5ca6a474d3

Adding/modifying a system (docs: Adding a System)

• Add/modify systems/system_name/system.py file
• Add/modify a dry run unit test for system_name in .github/workflows/run.yml
• Add/modify systems/all_hardware_descriptions/hardware_name/hardware_description.yaml which will appear in the docs catalogue

Adding/modifying a benchmark (docs: Adding a Benchmark)

• If modifying the source code of a benchmark: create, self-assign, and link here a follow up issue with a link to the PR in the benchmark repo.
• If package.py upstreamed to Spack is insufficient, add/modify repo/benchmark_name/package.py plus: create, self-assign, and link here a follow up issue with a link to the PR in the Spack repo.
• If application.py upstreamed to Ramble is insufficient, add/modify repo/benchmark_name/application.py plus: create, self-assign, and link here a follow up issue with a link to the PR in the Ramble repo.
• Tags in Ramble's application.py or in repo/benchmark_name/application.py will appear in the docs catalogue
• Add/modify an experiments/benchmark_name/experiment.py to define a single node and multi-node experiments
• Add/modify a dry run unit test in .github/workflows/run.yml

Adding/modifying core functionality, CI, or documentation:

• Update docs
• Update .github/workflows and .gitlab/tests unit tests (if needed)