Merge branch '344594-fix-migration' into '16-0-stable-ee'

What does this MR do and why?

Describe in detail what merge request is being backported and why

We are using the approach similar to !78562 (merged) for populating the project permissions for blobs. This migration iterates over the permutations of visibility_level and repository_access_level for all projects and updates blob documents with those levels. We also added the brute force way to make sure we are adding permissions to blobs without project join as well.

Why we need to backport it ?

We need to backport the migration because the older migration was taking alot of time and was a little buggy as well, Here are all the MRs for the fixes and the new approaches that we took:

• !117224 (merged)
• !118494 (merged)
• !119479 (merged)
• !121077 (merged)

MR acceptance checklist

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

• This MR is backporting a bug fix, documentation update, or spec fix, previously merged in the default branch.
• The original MR has been deployed to GitLab.com (not applicable for documentation or spec changes).
• This MR has a severity label assigned (if applicable).
• This MR has been approved by a maintainer (only one approval is required).
• Ensure the e2e:package-and-test-ee job has either succeeded or been approved by a Software Engineer in Test.

Note to the merge request author and maintainer

If you have questions about the patch release process, please:

• Refer to the patch release runbook for engineers and maintainers for guidance.
• Ask questions on the #releases Slack channel (internal only).