Add new versions to workflow and remove use of untainted

[markeganfuller]

• Add new ruby versions to workflow
• Remove use of deprecated untaint method.
  It was removed in https://bugs.ruby-lang.org/issues/16131

[chris-reeves]

Hey @markeganfuller, great to hear from you - I hope all is well with you!

Thanks for raising this PR - we definitely need to remove untaint to support recent (i.e. current!) ruby versions.

I'm not so keen on switching to anonymous block forwarding though, as that bumps the minimum required ruby version to 3.1 with no real benefit. Granted, even 3.1 is out of support now, but there are no doubt some users out there with ancient ruby versions and I'd rather not cause them unnecessary pain.

Would you mind dropping the anonymous block forwarding commit and reverting the required ruby version to 2.3.0? Could we also restore the older rubies to the testing matrix? I'm happy to drop older versions from the testing matrix if the latest Gemfile.lock ends up causing them issues, but lets at least give them a chance. :-)

[markeganfuller]

Hi @chris-reeves, things are slowly moving forward here as usual!

I've dropped the version updates (beyond 2.7.7 -> 2.7.8 as the lint failed to run) and anonymous forwarding.