Bump SPHT to v0.22 + adopt new syntax for applicable shortcodes

[agriyakhetarpal]

Brief description of what is fixed or changed

This PR bumps the theme to the new v0.22 release, adapting new syntax for figure, image, and button shortcodes via scientific-python/scientific-python-hugo-theme#674. This is building upon @goanpeca's work in #859. Closes #859.

[netlify]

❌ Deploy Preview for numpy-org failed.

Name	Link
🔨 Latest commit	0531473
🔍 Latest deploy log	https://app.netlify.com/projects/numpy-org/deploys/695286c4e373a50008565adf

[agriyakhetarpal]

Hi @stefanv – this should be ready. The CI is failing because the Ubuntu image needs to be updated on the Netlify admin side (the same error we had the other day).

[stefanv]

Who has access to numpy.org Netlify? Could you please update the Ubuntu build image to the latest.

[mattip]

Maybe @goanpeca (from #347) knows who is the netlify owner?

[rgommers]

Looks like a Netlify bug. There are only two options, Ubuntu Focal (20.04) and Noble (24.04). The latter is the default and is what's selected. But the former is used in CI, says the log:

build-image version: 235a96ed6c11cbdf942eed7e70e6802956f9b464 (focal)

[rgommers]

Unless I'm looking at the wrong Netlify Project of course. It doesn't look like I have access to the numpy-org project, only to numpy-preview. The latter no longer seems used. It is likely to be @goanpeca then.

[rgommers]

Okay, I deleted my old numpy-preview config to avoid confusion; it was definitely not used. After a lot of digging I found the answer: it's @stefanv that moved the config over and holds the keys. From a Slack DM on 6 Jan 2022:

"I moved Netlify for numpy.org PR previews over to a separate account that we can all hold the keys to. Currently it is on Gonzalo's personal one. Despite de-authorizing Netlify and re-installing it, it still builds Gonzalo's. I reached out to him via email to disable his numpy.org builds, ..." (after which Gonzalo deleted the other config)

I also have an email from Stefan with a GPG-encrypted Netlify key, but we never really used that system and I don't really feel like reverse-engineering it now. So let's just wait for @stefanv to make the change here.