Update Hugo to latest version

[codyro]

We pin Hugo to 0.98.0, while the latest version is 0.139.4. There have been a ton of QoL improvements, which we could and should leverage.

All that needs to be done for this is to verify that the site builds and runs cleanly (look for Hugo warnings and errors). If it doesn't, we'll want to fix whatever is wrong (EX, deprecated functions, etc.).

After that someone from the Infrastructure will verify everything and update the CloudFlare Pages version (HUGO_VERSION environmental).

Further context:
#709 (comment)

[alaurie]

I think the current build process is pulling the latest version regardless of any pinning done.

https://github.com/AlmaLinux/almalinux.org/actions/runs/12401185107/job/34620009233

[codyro]

I think the current build process is pulling the latest version regardless of any pinning done.

https://github.com/AlmaLinux/almalinux.org/actions/runs/12401185107/job/34620009233

Whoopsie doodle. You're right! I forgot we changed how we published the website a while ago, making that environmental variable unused.

For some context, we use Cloudflare Pages to serve the website. Previously, we had the website cloned and built on their end (https://developers.cloudflare.com/pages/framework-guides/deploy-a-hugo-site/#use-a-specific-or-newer-hugo-version). However, at some point, we needed to work around some gotcha and ended up using a GitHub action to build the website via a GH runner and then upload it to Cloudflare Pages. It looks like we never pinned a version in that action: https://github.com/AlmaLinux/almalinux.org/blob/master/.github/workflows/publish.yml#L21-L24

@jonathanspw We should consider pinning to a version to avoid accidentally pushing a broken version of the site unexpectedly. Thoughts?