If a repo was transferred, deployment permissions for admins won't work correctly

Issue Summary

When a repository is transferred, and a deployment environment exists with the "Only allow admins to deploy to this environment" restriction activated, admins will be unable to perform deployments to said environment.
An error message will state, when attempting to deploy to this environment as an admin, that you do not have access to this environment, regardless of your access level to this repo.

Steps to Reproduce

1. Create a deployment environment on a repository, and check "Only allow admins to deploy to this environment". Make sure you are an admin of this repository.
2. Transfer the repository where the deployment env was created between workspaces. Make sure to be an admin on the target repo for the transfer
3. Attempt to perform a deployment to the target environment
4. You will see an error message stating that you are not an admin.

Expected Results

Admins should be allowed to deploy to the created environment.

Actual Results

The below error message is thrown in Pipelines:

The Pipeline was paused because <user_who_triggered_the_build> tried to deploy, but only an admin can deploy to <target_environment>.

This error message will show up regardless of whether you are an admin or not.

Workaround

Re-creating the deployment environment in the transferred repository should fix the issue.