Disable ArkoseLabs feature flag globally in specs

ee/spec/features/users/arkose_labs_csp_spec.rb

@@ -5,6 +5,10 @@ require 'spec_helper'
 RSpec.describe 'ArkoseLabs content security policy' do
   let(:user) { create(:user) }
 
+  before do
+    stub_feature_flags(arkose_labs_login_challenge: true)
+  end
+
   it 'has proper Content Security Policy headers' do
     visit root_path
 

ee/spec/requests/api/captcha_check_spec.rb

@@ -21,6 +21,10 @@ RSpec.describe API::CaptchaCheck do
     end
 
     context 'when the feature flag arkose_labs_login_challenge is enabled' do
+      before do
+        stub_feature_flags(arkose_labs_login_challenge: true)
+      end
+
       context 'when the username is invalid' do
         let(:invalid_username) { 'invalidUsername' }
 

spec/spec_helper.rb

@@ -329,6 +329,10 @@ RSpec.configure do |config|
       stub_feature_flags(disable_anonymous_search: false)
       stub_feature_flags(disable_anonymous_project_search: false)
 
+      # Specs should not get a CAPTCHA challenge by default, this makes the sign-in flow simpler in
+      # most cases. We do test the CAPTCHA flow in the appropriate specs.
+      stub_feature_flags(arkose_labs_login_challenge: false)
+
       allow(Gitlab::GitalyClient).to receive(:can_use_disk?).and_return(enable_rugged)
     else
       unstub_all_feature_flags