Make MRs build using Ruby 3.2 by default
https://gitlab.com/gitlab-org/gitlab/-/pipeline_schedules
Proposal
As we move towards rolling out Ruby 3.2, we'd like to start:
- Building every MR using Ruby 3.2 by default
- Ensure if engineers wish to run the MR with Ruby 3.1 then the label pipeline:run-in-ruby3_1 works as expected for this
- We currently run a Ruby 3.0 pipeline every 2 hours. Now that we have been on Ruby 3.1 for a few months do we still need this?
CI builds would continue to use Ruby 3.1 for now until we move to the roll out of Ruby 3.2
Reasoning
This will give more focus to ensuring that MR are built/tested with Ruby 3.2, whilst the 2 hourly and CI builds running at 3.1 mean that changes are still being built and tested on the platform we currently deploy to (Ruby 3.1)