Manually update workflows to docker versions to test

[froggleston]

This PR will replace the current Workbench workflows with dockerised versions to improve a range of maintenance factors, and deliver more reproducible builds.

Addresses #650

This is still in testing phase, and can be safely reverted if issues arise.

[github-actions]

ℹ️ Modified Workflows

This pull request contains modified workflow files and no preview will be created.

Workflow files modified:

• .github/workflows/README.md
• .github/workflows/docker_apply_cache.yaml
• .github/workflows/docker_build_deploy.yaml
• .github/workflows/docker_pr_receive.yaml
• .github/workflows/pr-close-signal.yaml
• .github/workflows/pr-comment.yaml
• .github/workflows/pr-post-remove-branch.yaml
• .github/workflows/pr-preflight.yaml
• .github/workflows/pr-receive.yaml
• .github/workflows/sandpaper-main.yaml
• .github/workflows/sandpaper-version.txt
• .github/workflows/update-cache.yaml
• .github/workflows/update-workflows.yaml

If this is not from a trusted source, please inspect the changes for any malicious content.

[Bisaloo]

Just a quick check to avoid additional commits, but you might have done this already:

I suspect the swcarpentry GH organization restricts which actions can be used.

Do you need to move froggleston/actions as a branch in carpentries/actions or enable actions from your account? (no extra commit required for this second option)

[froggleston]

Just a quick check to avoid additional commits, but you might have done this already:

I suspect the swcarpentry GH organization restricts which actions can be used.

Do you need to move froggleston/actions as a branch in carpentries/actions or enable actions from your account? (no extra commit required for this second option)

I've merged in the changes to the main carpentries actions - they're non-breaking for existing workflows.

[Bisaloo]

I'm not 100% sure if you are still editing things but I'm approving this PR so feel free to merge when convenient for you.

[froggleston]

Thanks @Bisaloo ! Here we go .... 🤞

[froggleston]

@Bisaloo Looks good! There were a couple of minor issues but none that stopped the build from working, just things I'll need to document and improve (the build is quite verbose as there are more checks now than before).

[Bisaloo]

It's not really a problem in this specific case but might(?) be in other lessons: the png files created by rmarkdown are larger than what they used to be. I can't pinpoint the exact reason for this but my intuition would be:

• either pngquant used to be present and is no longer there. Knitr has a hook to automatically compress png as they are rendered if pngquant is installed and the hook is enabled.
• or the graphical backend is different. In particular, the ragg package probably produces png smaller than Cairo. I'm not sure which one was used before and which one is used now.

Again, this may not warrant a deep dive now but it's probably good to keep in the back of your mind.

[froggleston]

That's great feedback - thank you! I can add pngquant to the docker image for the next release. I'm not doing anything with any internals, so haven't switched any backend rendering specifically.