Fix protected envs multi-db test

Locally, this test was failing because the configurations for the test
environment were empty. If they are empty, we won't raise the
appropriate error.

In the Rails test suite locally the environment in this test is
`default_env`, but in CI it's `test`. We can fix this by pass `env` to
`check_protected_environment!` instead of passing a string of the
enviornment.

Followup to rails#46340

Author: eileencodes

activerecord/test/cases/tasks/database_tasks_test.rb

@@ -154,6 +154,7 @@ class DatabaseTasksCheckProtectedEnvironmentsMultiDatabaseTest < ActiveRecord::T
 
       def test_with_multiple_databases
         env = ActiveRecord::ConnectionHandling::DEFAULT_ENV.call
+
         with_multi_db_configurations(env) do
           protected_environments = ActiveRecord::Base.protected_environments
           current_env = ActiveRecord::Base.connection.migration_context.current_environment
@@ -167,7 +168,7 @@ def test_with_multiple_databases
 
           assert_not_includes protected_environments, current_env
           # Assert not raises
-          ActiveRecord::Tasks::DatabaseTasks.check_protected_environments!("test")
+          ActiveRecord::Tasks::DatabaseTasks.check_protected_environments!(env)
 
           ActiveRecord::Base.establish_connection(:secondary)
           connection = ActiveRecord::Base.connection
@@ -176,8 +177,9 @@ def test_with_multiple_databases
           schema_migration.create_version("1")
 
           ActiveRecord::Base.protected_environments = [current_env.to_sym]
+
           assert_raise(ActiveRecord::ProtectedEnvironmentError) do
-            ActiveRecord::Tasks::DatabaseTasks.check_protected_environments!("test")
+            ActiveRecord::Tasks::DatabaseTasks.check_protected_environments!(env)
           end
         ensure
           ActiveRecord::Base.protected_environments = protected_environments