Mirror authorization is not repeatable in the UI after declining

Issue Summary

Declining mirror authorization removes the authorization request on the upstream but leaves the mirror setup referencing the declined request. There is no way in the UI to repeat the authorization request and the mirror setup page links to a 404 page on the upstream.

This is reproducible on Data Center: yes

Steps to Reproduce

1. Create a new mirror or delete an existing mirror from the Bitbucket UI (removing authorization for the mirror).
2. Click the "Go to the primary server" button on the mirror setup page which will redirect to the upstream.
3. Click "Decline" to decline the authorization request.
4. Go back to the mirror and click the "Go to the primary server" button again.

Expected Results

The mirror either automatically creates another authorization request after the initial request is declined, or the mirror setup UI indicates no authorization request exists with the option to manually create a request.

Actual Results

Clicking on the "Go to the primary server" button on the mirror results in a 404 page on the upstream (at e.g. [host:port]/plugins/servlet/admin/mirrors/farm/[request_id]/authorize). No additional authorization requests are automatically created after the declined request and the mirror setup UI still references the existing declined request.

Workaround

Visit the mirror with reconnect=1 added the URL (e.g. [host:port]/mirror/mirror?reconnect=1). This will trigger another authorization request to be created. The "Go to the primary server" button will then redirect the user to the authorization request on the upstream which can be accepted.