5-minute delay in Update Now mirror button is inconvenient
<!--IssueSummary start-->
<details>
<summary>
Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards.
</summary>
- [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=3390)
</details>
<!--IssueSummary end-->
### Description
GitLab EE limits the frequency with which mirror updates can be pulled to no more than once every five minutes. The can delay critical changes from being mirrored.
It appears that this limitation has primarily been implemented to prevent problems at GitLab.com scale.
We should make the maximum mirror frequency configurable by instance to allow EE users to customize this to their needs. This will allow customers to manually trigger an update more frequently than every 5 minutes./
At least one customer deploys from a mirrored repository, which can delay hot fixes being deployed by up to five minutes.
### Proposal
- Add configurable `mirror_max_frequency` (or similar) to limit the frequency with which a project can be mirrored
### Links / references
https://gitlab.zendesk.com/agent/tickets/82019
https://www.youtube.com/watch?v=sUztI4Lx-fQ
### More info
* For repo mirroring for CI purposes follow https://gitlab.com/gitlab-org/gitlab/-/issues/237891
issue