[ci] fix CI by replacing deprecated Xcode versions, and add Xcode 14, Xcode 15, and Ruby 3.1 to test envs

[rogerluan]

Checklist

• I've run bundle exec rspec from the root directory to see all new and existing tests pass
• I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
• I see several green ci/circleci builds in the "All checks have passed" section of my PR (connect CircleCI to GitHub if not)
• I've updated the documentation if necessary.

Motivation and Context

The goal of this PR is to fix CI (master doesn't build) and update the Xcode versions where our tests are run.

Description

master is failing because it still tries to use old (now unsupported) envs:

Example of failing builds:

• Xcode 11.7.0: https://app.circleci.com/pipelines/github/fastlane/fastlane/5433/workflows/f4bc049e-57bd-4c3f-b21e-f582618cfc84/jobs/89907
• Xcode 13.0.0: https://app.circleci.com/pipelines/github/fastlane/fastlane/5433/workflows/f4bc049e-57bd-4c3f-b21e-f582618cfc84/jobs/89906

These are the supported envs currently:

https://circleci.com/docs/using-macos/

After setting the new versions of Xcode and their respective Ruby versions, I realized that there are other indirect dependencies that either gets updated (Ruby's openssl) or need to be updated (http-cookie, used by Faraday), so some further changes needed to take place in the rspecs and dependency versions.

I don't understand how the specs were passing on Ruby 3.1 in other environments 🤔

CLICK ME to understand "how come Ruby 3.1 was working before and it suddenly broke?"

Some context regarding Ruby 3.1... This wasn't the first Ruby 3.1 image to be used and now it got broken, so I was wondering "how come this was working before and it suddenly broke?"

Turns out that for Ruby 3.0, CircleCI used to work fine (build 1), and by using an identifier such as 3.0 it would set ruby version to the latest 3.0.*, 3.0.2 in this case. But for Ruby 3.1, CircleCI used to fail silently 😅 (build 2), and then it would default to Ruby 2.7.x (whatever the default of the machine was).

So the reality is that apparently we never ran CI on Ruby 3.1, hence why I'm finding some long-broken things when running on Ruby 3.1 (e.g. openssl got updated in Ruby 3.1 and this breaks stuff).

On top of that, the behavior of "setting 3.0, and it installing the closest known version e.g. 3.0.2" that used to work, no longer works AFAICT. I set Ruby 3.1 and 3.2 and it didn't recognize it (build 3), but when I set 3.1.2 (which is the version I saw that is installed in CircleCI's image), it installed correctly (build 4).

So these are the reasons why the old "3.1" identifier used to work (cuz it'd fail silently and fallback to 2.7.x), and why the "3.0" identifier used to work (because it'd automatically pick 3.0.2, but it no longer does that)

Resources

• Creating a root CA certificate and an end-entity certificate
• My Stack Overflow answer explaining how to solve the new OpenSSL syntax: https://stackoverflow.com/a/76915458/4075379
• OpenSSL 3.1 documentation on OpenSSL::PKey::EC: https://ruby-doc.org/stdlib-3.1.0/libdoc/openssl/rdoc/OpenSSL/PKey/EC.html
• Issue reported on http-cookie on Ruby 3: Tests fail on http-cookie / ruby 3.0 sparklemotion/http-cookie#38
• Fix for the yaml cookie parsing issue: sparklemotion/http-cookie@d12449a

Testing Steps

Just pass CI:

_{Screenshot taken from adac361}

[rogerluan]

Welp

https://status.circleci.com

Let's wait.

[rogerluan]

There's still these 2 failures to fix, I forgot 😓

Working on them...

[rogerluan]

The reason those specs are failing is because the current version of Rubocop doesn't support Ruby 3.1, so it needs to be upgraded (it's currently frozen at a specific old version). Upgrading it requires a lot of changes throughout the codebase 😅 or adding them as 'todo'...

[rogerluan]

Reviewed 1 rule being applied and then added the remaining of them to the Rubocop TODO file via rubocop --regenerate-todo 😬 most sane way to do this right now (given the scope of this PR). We can revisit the TODO file later.

[fastlane-bot-helper]

	1 Warning
⚠️	Big PR

Generated by 🚫 Danger

[rogerluan]

3 crashes seen when running tests against Ruby 3.2:

Fixing them by upgrading fakefs…

[rogerluan]

Ugh. There are some issues with Ruby 3.2...

I'll probably cut this out of this PR's scope and stick with Ruby 3.1 only.

[rogerluan]

Self-reviewed 👍

[rogerluan]

These diffs look huge but 99% of the changes I made was just sorting the gems alphabetically 😅

[rogerluan]

Noting down the discoveries related to Ruby 3.2:

• We need to bump fakefs from 1.2 to at least 1.8 (even though fakefs's changelog state that support to Ruby 3.2 is only added on 1.9, it works on 1.8)
  • We can't update to 1.9 because it drops support to Ruby 2.6, which we intend to keep for as long as the default macOS's Ruby version is still at 2.6.
• We need to bump rspec to 3.12.2 at least, to fix 7 broken rspecs when running in Ruby 3.2.
  • Changelog: https://github.com/rspec/rspec-mocks/blob/main/Changelog.md#3122--2023-01-07
• When upgrading rspec from 3.10.x to 3.11.x, another 19 failures pop up:

tl;dr: the next PR should set fakefs to 1.8, rspec to latest, and then work on fixing those 19 rspecs on our end.

[getaaron]

Approved pending the MFA changes.

The biggest thing to happen to fastlane… since fastlane