Tidy up Ruby 3.2 pipelines

Summary

Now that we have rolled out Ruby 3.2, we can tidy up the pipeline schedules

Suggested approach

As of now syncing to the ruby3_2 branch and then running a Ruby 3.2 pipeline is not needed as we have updated master to use Ruby 3.2, we could simply turn off these schedules?

We will want to create a similar set up for Ruby 3.3 at some point in the near future, but have not begun any work to assess what is broken with Ruby 3.3 yet. Perhaps we could set things up in preparation for this, but not schedule the pipelines to run on a schedule just yet?