Add Ruby 3.1 to build

Ruby 3.2 contains a number of kwargs fixes, and Rails 7 may be a
prerequisite for Ruby 3.2. We'll want to test and deploy Ruby 3.1
before jumping to 3.2.

Ruby 3.1 requires at least rubygems v3.1.3. Let's just bump
everything to 3.4, and consolidate the Ruby 3.2 build.

.gitlab/ci/gitlab.images.yml

@@ -13,26 +13,6 @@ gitlab:
   extends:
     - .gitlab
   stage: gitlab
-  variables:
-    RUBYGEMS: '3.2'
-    LFS: '2.9'
-    YARN: '1.22'
-    GRAPHICSMAGICK: '1.3.36'
-    ARCH: linux/amd64,linux/arm64
-  parallel:
-    matrix:
-      - OS: ['debian:bullseye']
-        RUBY: ['2.7.patched', '3.0.patched']
-        GIT: ['2.36']
-        POSTGRESQL: ['11', '12', '13']
-        GOLANG: ['1.18', '1.19']
-        RUST: ['1.65']
-        NODE: ['16.14', '18.12']
-        CHROME: ['106', '109']
-
-gitlab-ruby-3.2:
-  extends:
-    - .gitlab
   variables:
     RUBYGEMS: '3.4'
     LFS: '2.9'
@@ -42,13 +22,13 @@ gitlab-ruby-3.2:
   parallel:
     matrix:
       - OS: ['debian:bullseye']
-        RUBY: ['3.2.patched']
+        RUBY: ['2.7.patched', '3.0.patched', '3.1.patched', '3.2.patched']
         GIT: ['2.36']
         POSTGRESQL: ['11', '12', '13']
-        GOLANG: ['1.19']
+        GOLANG: ['1.18', '1.19']
         RUST: ['1.65']
-        NODE: ['16.14']
-        CHROME: ['109']
+        NODE: ['16.14', '18.12']
+        CHROME: ['106', '109']
 
 # Used by GitLab's compile-production-assets and compile-test-assets jobs
 gitlab-assets:
@@ -56,7 +36,7 @@ gitlab-assets:
     - .gitlab
   stage: gitlab-assets
   variables:
-    RUBYGEMS: '3.2'
+    RUBYGEMS: '3.4'
     LFS: '2.9'
     YARN: '1.22'
     GRAPHICSMAGICK: '1.3.36'
@@ -64,7 +44,7 @@ gitlab-assets:
   parallel:
     matrix:
       - OS: ['debian:bullseye']
-        RUBY: ['2.7', '3.0']
+        RUBY: ['2.7', '3.0', '3.1', '3.2']
         GIT: ['2.33']
         NODE: ['16.14', '18.12']