Use official Ruby setup GH action

[seshrs]

This is a CI fix (housekeeping).

Summary

I noticed that the CI results in #8587 mentioned that actions/setup-ruby is no longer maintained and that we should migrate to using ruby/setup-ruby instead.

This PR updates jobs to use ruby/setup-ruby. I'm not super-familiar with Ruby and had to guess which steps were obsolete with the new action. Hopefully, the GH Actions results on this PR will help evaluate whether I got it right! 😅

EDIT: Haha that didn't work. Will try debugging later this week.

[seshrs]

Oh I see some overlap with #8610. Will wait for that to merge first.

[MichaelCurrin]

Looks good but I see there are conflicts to fix and this is WIP.

[MichaelCurrin]

Fix conflicting file.

[seshrs]

@MichaelCurrin yes you were right, the bundle env variables had to be declared at the job-level so that other steps use the correct bundle config! Thanks for pointing that out 😃

Given that the Third-Party Repository Profiling workflow completed successfully, I think we have more confidence that the docs workflow will also work when this PR is merged with master.

[MichaelCurrin]

Yes good that the checks are passing.

And the job is setup to run on a PR against master and will work the same once merged.

[MichaelCurrin]

You can find your branch marked with passing runs on the Actions tab

https://github.com/jekyll/jekyll/actions

[seshrs]

Hi @MichaelCurrin, sorry I dropped the ball for a couple of weeks 😅

Is there some further action needed from me to push this PR forward?

[MichaelCurrin]

No PR changes are outstanding. This just needs a review and merging by a maintainer - a reviewer with write access

[parkr]

Looks good to me!

I wasn't able to fully validate the bundler-cache option but I'm assuming we'll be able to continue benefitting from the Actions cache.

[MichaelCurrin]

More info on bundler cache flag here:

https://github.com/ruby/setup-ruby#single-job

That means that in this PR, we use the ruby/setup-ruby action to handle Bundle itself, bundle install step and cache of gems too. And so the cache action and the gem install steps are unnecessary and are good to be taken out.

[DirtyF]

@jekyll: merge +dev