Update CI workflows

[ahueck]

The current workflows (CI, CI-ext) are sequential. This could be changed by using multi-job workflows, saving some execution time.

Pre-requisites

To avoid too much code/steps duplication, recent composite actions can be used depending on implementation state, see 1. Next Steps for Fully Functioning Composite Actions and 2. composite-run-steps-actions

• Action for setup of Clang/LLVM/OpenMPI package
  • Can this include the environment setup for the LLVM executables?
  • Can we set GITHUB_ENV values in a composite action?

Side effects

Artifacts are generated per job, e.g., 2 files are generated for the CI workflow: 1. coverage html report and 2. lulesh build/run data.

CI

Parallel Jobs:

1. Build for coverage/testing

OMP Extension

Build matrix to test different thread-safety levels for the TypeART runtime libary.

• Combine coverage of all levels (safeptr, mutex, unsafe)

CI-ext

Parallel Jobs with and without thread-safety enabled:

1. test-bench

• Dividing the subprojects probably too much overhead

2. AD test-bench
3. OMP test-bench