Explicitly mark cross-database modification for `dast_*_profile`

Since this issue is not yet resolved (and needs to be) lets ackonwledge
it for now to have the allowlist empty.

Related issue: https://gitlab.com/gitlab-org/gitlab/-/issues/350051

ee/spec/services/ci/retry_build_service_spec.rb

@@ -38,10 +38,12 @@ RSpec.describe Ci::RetryBuildService do
         end
 
         it 'clones the profile associations', :aggregate_failures do
+          ::Gitlab::Database::QueryAnalyzers::PreventCrossDatabaseModification.allow_cross_database_modification_within_transaction(url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/350051') do
             expect(new_build.dast_site_profile).to eq(dast_site_profile)
             expect(new_build.dast_scanner_profile).to eq(dast_scanner_profile)
           end
         end
+      end
 
       context 'when build has secrets' do
         let(:secrets) do

spec/support/database/cross-database-modification-allowlist.yml

 - "./ee/spec/replicators/geo/terraform_state_version_replicator_spec.rb"
-- "./ee/spec/services/ci/retry_build_service_spec.rb"
 - "./spec/features/issues/issue_detail_spec.rb"
 - "./spec/features/projects/pipelines/pipeline_spec.rb"
 - "./spec/features/signed_commits_spec.rb"