[ci] Migrate CircleCI to Ruby 3.3, fix CI

[iBotPeaches]

Problem

The CI platform on docs is built from an outdated DockerHub account only in the hands of Josh. I tried for about a year to get keys/access to that account, but failed. This meant as we moved fastlane/fastlane to new minimum Ruby versions, docs fell behind unable to be built/deployed.

Solution

I've created a new DockerHub account and published images with full automation here. I've ported the changes from fastlane/fastlane in terms of CI (fastlane/fastlane#29753) to bring this CI pipeline to modernization.

[iBotPeaches]

Hmmm. So the challenge here is you need Python (mkdocs) and Ruby (fastlane) and doing that with native Docker images is a challenge.

I will return to the fastlane/docker repo to bring an updated Ruby 3.x image that includes Python 3.8 and then setup some CI/CD for automated deploys to DockerHub. Since it seems that image is really dependent on this setup.

Alternatively with GitHub Actions, we could just install Ruby/Python with setup-python/setup-ruby, but extracting all the secrets and flows from this working CircleCI would present a challenge.

[iBotPeaches]

PR opened on docker - I may test with my forked image here in meantime - fastlane/docker#11

[iBotPeaches]

Cool - updated docker image works (fastlane/docker#11). I'll await that being merged/tagged and come back here to finish this branch.

[rogerluan]

Should this point to our image?

[iBotPeaches]

Good catch. Aligned it in latest commit