Standardizing system names

[pearce8]

Description

Making system names follow site-system name conventions.

Dependencies: none.

Fixes issue(s): none.

Type of Change

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

Checklist:

If adding/modifying a system:

• {X} Create a new directory for the system and a new system.py file
• {X} Add a new dry run unit test in .github/workflows
• {X} 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)

[pearce8]

@rfhaque Can you please figure out what I missed in the dry runs, and review? I would like to merge this to make our system naming more uniform.