Require capybara >= 3.40 for Rack 3

This dependabot bump re-resolved rack from 2.2.23 to 3.2.6, which removed
the Rack::Handler namespace. Capybara 3.39.2 hardcodes Rack::Handler::Puma
when booting its test server, and puma 7 only registers its handler under
Rackup::Handler::Puma when Rack 3 is loaded, so every spec that booted the
Capybara server failed with `uninitialized constant Rack::Handler`.

Capybara 3.40.0 falls back to Rackup::Handler::Puma. Gemfile.next.lock was
already on 3.40.0, which is why the rails-next build stayed green.

Author: JuanVqz

Gemfile

@@ -85,7 +85,9 @@ end
 
 group :test do
   gem "apparition", git: "https://github.com/twalpole/apparition.git", ref: "7db58cc6b0e4ca4141b074ff27d5936a1b8874bf"
-  gem "capybara"
+  # 3.40+ needed for Rack 3: earlier versions reference the removed
+  # Rack::Handler::Puma constant when booting the test server
+  gem "capybara", ">= 3.40"
   gem "webdrivers"
   gem "database_cleaner-active_record", ">= 2.1.0"
   gem "capybara-screenshot"

Gemfile.lock

@@ -104,11 +104,11 @@ GEM
       thor (~> 1.0)
     builder (3.3.0)
     byebug (11.1.3)
-    capybara (3.39.2)
+    capybara (3.40.0)
       addressable
       matrix
       mini_mime (>= 0.1.3)
-      nokogiri (~> 1.8)
+      nokogiri (~> 1.11)
       rack (>= 1.6.0)
       rack-test (>= 0.6.3)
       regexp_parser (>= 1.5, < 3.0)
@@ -528,7 +528,7 @@ DEPENDENCIES
   bootstrap-sass (= 3.4.1)
   bourbon
   byebug
-  capybara
+  capybara (>= 3.40)
   capybara-screenshot
   coffee-script
   csv

Gemfile.next.lock

@@ -559,7 +559,7 @@ DEPENDENCIES
   bootstrap-sass (= 3.4.1)
   bourbon
   byebug
-  capybara
+  capybara (>= 3.40)
   capybara-screenshot
   coffee-script
   csv