Add Workflows for generating reference results

[valentin-seitz]

This PR adds a reusable workflow to automagically add reference results to a certain branch.
It can be either be triggered manual or another trigger can be used to trigger the reusable workflow (e.g on creation of PR of a certain form)

It also adds more information on the machine (Still open to discussion if we acually need it). But especially the CPU ISA Extensions like AVX-512 etc are of importance.

The Pipeline now runs and is able to add commits: https://github.com/precice/tutorials/actions/runs/7181615150

[valentin-seitz]

This PR is now ready.
The CI/CD Pipeline works as expected (see: https://github.com/precice/tutorials/actions/runs/7181615150)
After #420 is merged, i will rebase and then the tests should go through so we can merge.

[valentin-seitz]

I also added small changes to the Dockerfile to allow for commit-ish things to be requested.

[MakisH]

The implementation looks very nice!
Some comments to consider, feel free to merge afterwards.

[MakisH]

Closes #405.

This is related to #401 (git hash reporting) by requiring (only via documentation) specific Git commit or tag (not branches, which can change over time) when generating reference results. I would still feel safer if I had a dump of all hashes in one log file, but I remember from our last meeting that this is complicated due to the current architecture. I assume it still creates the same report for the current/tested results. So, yes, it closes #401 as well.

Regarding #400 (contents of the archive):

• reference_data is renamed to reference-results
• TUTORIALS_REF is included in the report
• I have not checked what the actual contents are, because I don't have an archive readily available, but I still believe it closes Contents of the system tests archive #400.