Validate auth gems with Ruby 3.1 and 3.2

Previously as part of Ruby 3 upgrade, we manually tested each of the gems within ~"group::authentication and authorization" via &9578 (closed). As we move to upgrade to Ruby 3.1/3.2, a similar test is needed however many of the gems don't have thorough UT coverage and manually testing each one (with the respective local setup) is considerable effort for a minor version.

It's proposed that we update the status for the auth owned gems in #404750 (closed) excel sheet and simply build them locally with 3.1/3.2 to verify compatibility.

Proposal

@jessieay recommended, rather than manually testing each OAuth library without a CI build against Ruby 3.0+ as we did for Ruby 3.0, do 3 things for each gem without a CI build:

1. Check for newer releases of the gem that might have been released to handle Ruby upgrade / compatibility.
2. If there is a new release:
   1. Upgrade the gem
3. If no new release:
   1. Upgrade Ruby locally and make sure that bundle install for the gem version we are on still works
   2. Look at the list of compatibility issues for Ruby 3.1 and Ruby 3.2 and ensure that none of those changes will affect the source code of the gem (search for existence of any methods that were removed).