Clearly identify which PyLith version is associated with the benchmark parameter files

[baagaard-usgs]

The benchmarks were created over a period of time and updated irregularly. As a result, it isn't clear which version of PyLith can be used to run a benchmark.

1. We should update the relevant benchmarks to the current version of PyLith.
2. For each benchmark we should clearly identify which version of PyLith will work.
3. Obsolete benchmarks should be marked accordingly.

[baagaard-usgs]

This is now easily done using the simulation metadata; however, this does not account for changes to Cubit and being able to generate the mesh files. This should be documented separately. We should also archive the mesh files (and output) on Zenodo, or another similar location to facilitate reproducibility.