<!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> Add a GitLab REST API endpoint to force a repository / project mirror update. At the moment, the latest documentation for GitLab 15.8 does not include a REST API endpoint to call, that would force an update / refresh operation on a configured GitLab repository mirror. In the GitLab web UI, under the repository settings for mirroring, there is a clickable button that forces an update of a remote mirror. My recommendation is to add a new REST API endpoint, that would allow a developer to force update a specific (or all) mirror configurations, for a given GitLab repository / project. Here are the current docs for GitLab mirrors: https://docs.gitlab.com/ee/api/remote_mirrors.html <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> <!-- Label reminders Use the following resources to find the appropriate labels: - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->