Experiment with job-context action

[omus]

Prototyping a new GHA job-context which is meant for determining the job name and id which are things both not available via GHA contexts.

In particular this actions allows runnings jobs to determine their own job name and job ID which is useful when interacting with the GitHub API. The intent is to use this action so that the matrix-output job can include the job ID as part of the artifact name.

One relevant implementation detail is that this action makes use of multiple GitHub contexts in order to generate the job name. Without these contexts we couldn't fill in the allows GitHub expressions which can be present in a job name. If we could solve this problem in another way we may be able to allow the use of a user specified job key.

[omus]

Noticed that you can use name: ${{ github.job }} but if I end up using name: ${{ github.job }} - ${{ matrix.index }} then ${{ github.job }} is empty for the GitHub rendered job name...

[omus]

Superseded by beacon-biosignals/job-context#1