release actions

[jpiesing]

1. Rename tests that are "beta" so they appear as "beta" in the test runner (Fraunhofer)​
2. Tag release in github (Fraunhofer+Resillion)​
3. Final check of user documentation for consistency​
4. Complete agreed release documentation based on results of final Fraunhofer sanity check (Bill Rose+Fraunhofer)​

[jpiesing]

2024-05-28: Proposal to change file added for pre-configured tests to list validated and beta. Same as was done for list of HbbTV tests. No need for renaming and re-generating tests. Probably lower risk of breaking anything else. Enable selecting validated or validated.

[FritzHeiden]

1. While the implementation is done we still need verification for the subsets (released and beta) as well as a page that explains what it means for a test to be released, beta or none, which can be linked in the config page.
2. The test runner is now tagged (https://github.com/cta-wave/dpctf-test-runner/releases/tag/v2.0.0).
   Tagging the tests repo depends on solving 1.

[jpiesing]

Can we close this? I think so.