Fix issues with require "bundler/setup"

If your ruby's bundler is different from the saved result in
`Gemfile.lock`, bundler autoswitches by starting a new process. When it
does this it sometimes doesn't pick up the old LOAD_PATH and results in
a LoadError.

Switch to use `Bundler.setup`, which is a simpler process and uses the
current bundler.

Author: luke-gruber

harness/harness-common.rb

@@ -44,7 +44,12 @@ def use_gemfile(extra_setup_cmd: nil)
   setup_cmds(["bundle check 2> /dev/null || bundle install", extra_setup_cmd].compact)
 
   # Need to be in the appropriate directory for this...
-  require "bundler/setup"
+  require "bundler"
+  # Use Bundler.setup instead of require 'bundler/setup' to avoid bundler's autoswitch restarting the
+  # process and messing with LOAD_PATH. Autoswitching occurs when the BUNDLED_WITH in the Gemfile.lock
+  # is a different version than the loaded version of bundler. This can happen in development when
+  # switching between ruby versions.
+  Bundler.setup
 end
 
 # This returns its best estimate of the Resident Set Size in bytes.