[Exploratory] Starting a script for llnl-weekly suite

[pearce8]

Description

• How to curate a suite
• How to report what is in a suite

Dependencies: FIXME:Add a list of any dependencies.

Fixes issue(s): FIXME:Add list of relevant issues.

Type of Change

• { } Adding a system, benchmark, or experiment
• { } Modifying an existing system, benchmark, or experiment
• { } Documentation update
• { } Build/CI update
• { } Benchpark core functionality

Checklist:

If adding/modifying a system:

• { } Create a new directory for the system and a new system.py file
• { } Add a new dry run unit test in .github/workflows
• { } System appears in System Specifications table in docs catalogue section

If adding/modifying a benchpark:

• { } Add a new application.py and (maybe) package.py under a new directory
  for this benchmark
• { } Configure an experiment
• { } Benchmark appears in Benchmarks and Experiments table in docs catalogue
  section

If adding/modifying a experiment:

• { } Extend experiment.py under existing directory for specific benchmark
• { } Define a single node and multi-node experiments

If adding/modifying core functionality:

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

[becker33]

Dumping thoughts here:

1. Discussed adding a top-level directory for suites
2. Suites would be composed of a set of experiments
3. Ideally this would involve cool ramble composition (see the work for composable environments in Spack) but would probably start out as scripts

@pearce8 does that cover what we had discussed so far?