Swap FK ci_daily_build_group_report_results to projects for LFK

What does this MR do and why?

Per &7249 (closed)

As part of our CI "decomposition" efforts we need to remove all foreign keys that are cross-database (ie. between the planned main and ci databases). We are going to replace them all with "loose foreign keys".

This foreign key have been determined to be safe for swapping to loose foreign keys per #348267 (closed).

We use Ci::DailyBuildGroupReportResult.project_id to build coverage analytic at the project level. Impossible to access the analytic page (groups/group_id/project_id/-/graphs/master/charts) without a project_id.

Related issue: #348267 (closed)

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

db/post_migrate/20220112232723_remove_projects_ci_daily_build_group_report_results_project_id_fk.rb

@@ -5,6 +5,7 @@ class RemoveProjectsCiDailyBuildGroupReportResultsProjectIdFk < Gitlab::Database
 
   def up
     with_lock_retries do
+      execute('LOCK projects, ci_daily_build_group_report_results IN ACCESS EXCLUSIVE MODE')
       remove_foreign_key_if_exists(:ci_daily_build_group_report_results, :projects, name: "fk_rails_0667f7608c")
     end
   end