Don't let Rails auto-enable YJIT when benchmarking CRuby baseline

Author: rwstauner

benchmarks/erubi-rails/config/environments/production.rb

@@ -92,4 +92,7 @@
 
   # yjit-bench configurations
   config.active_record.sqlite3_production_warning = false
+  # If we want to benchmark with YJIT then it has already been enabled by command line arguments.
+  # If we are benchmarking CRuby without YJIT don't enable it even if this build has it.
+  config.yjit = false
 end

benchmarks/lobsters/config/environments/production.rb

@@ -91,4 +91,7 @@
   config.active_record.sqlite3_production_warning = false
   config.logger = nil
   config.secret_key_base = 'in general secret should not be in the git repo but this is a benchmark'
+  # If we want to benchmark with YJIT then it has already been enabled by command line arguments.
+  # If we are benchmarking CRuby without YJIT don't enable it even if this build has it.
+  config.yjit = false
 end

benchmarks/railsbench/config/environments/production.rb

@@ -94,4 +94,7 @@
   config.active_record.sqlite3_production_warning = false
   config.logger = nil
   config.secret_key_base = 'in general secret should not be in the git repo but this is a benchmark'
+  # If we want to benchmark with YJIT then it has already been enabled by command line arguments.
+  # If we are benchmarking CRuby without YJIT don't enable it even if this build has it.
+  config.yjit = false
 end