Run zizmor on github actions, pinning all actions

[oliverguenther]

• Pin all github actions to shas, not tags
• Use persist-credentials: false where applicable
• Avoid more template interpolation

https://community.openproject.org/work_packages/74698

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

[machisuji]

:+1 LGTM! Although could you please elaborate a bit on the reason behind disabling package manager caching? Yes, it's probably a security issue. But it would just be interesting to see why this was disabled in the commit message, not just that it has been disabled.

[oliverguenther]

@machisuji from https://docs.zizmor.sh/audits/#cache-poisoning

This vulnerability happens when release workflows leverage build state cached from previous workflow executions, in general on top of the aforementioned actions or similar ones. The publication of artifacts usually happens driven by trigger events like release or events with path filters like push (e.g. for tags).

We could probably disable this only for dockerization/release processes, and leave the CI runs unchanged, and set it to ignore the respective actions.