Pin aruba to >= 2.0 to prevent silent fallback to 0.14.x

Cucumber 11 (Ruby >= 3.2 only) is incompatible with aruba 2.x.
Without a version constraint, bundler silently falls back to
aruba 0.14.14, breaking all cucumber scenarios due to API
incompatibilities.

Author: sferik

Gemfile

@@ -5,7 +5,7 @@ source "https://rubygems.org"
 group :development do
   gem "nokogiri"
   gem "cuprite"
-  gem "aruba"
+  gem "aruba", "~> 2.0"
   gem "capybara"
   gem "rackup"
   gem "cucumber"

Gemfile.lock

@@ -17,8 +17,8 @@ GEM
     ast (2.4.3)
     base64 (0.3.0)
     benchmark-ips (2.14.0)
-    bigdecimal (4.1.0)
-    bigdecimal (4.1.0-java)
+    bigdecimal (4.1.1)
+    bigdecimal (4.1.1-java)
     builder (3.3.0)
     capybara (3.40.0)
       addressable
@@ -54,7 +54,7 @@ GEM
       cucumber-messages (>= 31, < 33)
     cucumber-html-formatter (22.3.0)
       cucumber-messages (> 23, < 33)
-    cucumber-messages (32.2.0)
+    cucumber-messages (32.3.1)
     cucumber-tag-expressions (8.1.0)
     cuprite (0.17)
       capybara (~> 3.0)
@@ -159,7 +159,7 @@ PLATFORMS
   universal-java-11
 
 DEPENDENCIES
-  aruba
+  aruba (~> 2.0)
   benchmark-ips
   capybara
   cucumber