Reenable ci workflow

[Skenvy]

Description

Fixes #393

Update ruby version + bundler version

Ran docker run --entrypoint "/bin/bash" --rm -it ghcr.io/actions/jekyll-build-pages:v1.0.13 (currently latest) and got bundle --version of 2.5.11 and ruby --version of 3.3.4

Both versions needed to be upgraded as ruby 3.3 defaulted to bundler 2.1.2 which had ~11k lines of errors/warnings when running the bundle exec jekyll build.

permissions: {}

Workflow sends the token to a 3rd-party (not actions/...-owned) action, so explicitly set the permissions to none.

Refresh Gemfile.lock

Some of the previous gems in the lockfile weren't happy / had errors themselves when running jekyll, so refreshed the lockfile.

Caution

The failure in the workflow is due to it working again but the checker action is finding a problem url on one of the pages, not introduced by this.

Warning

Locally, rebuilt Gemfile.lock with ruby 3.3.6 because it was the only binary ruby for my platform, which came with bundler 2.5.22, so the Gemfile.lock has a BUNDLED WITH version that surpasses the version of the latest image used in the default gh-pages build that was used to set the bundler version in this's ci workflow. But the workflow ran fine with it (despite encountering an intentional error on the html check finding a problem url on the utilities page).

Tip

If at some point a recipe / script for renewing the lockfile that itself is version locked to some specific bundler version, the ruby/setup-ruby action's bundler argument could be changed to "Gemfile.lock"

Copyright Assignment

• This document is covered by the MIT License, and I agree to contribute this PR under the terms of the license.

[unixorn]

lgtm