Unsuccessful OAuth events sent to Jira Cloud cause dev status to be out of sync

Issue Summary

When an event is sent from Bitbucket DC to Jira Cloud via OAuth it can fail due to network issues, bug or a Jira Cloud outage.

When this occurs the development panel in Jira cloud becomes out of sync with Bitbucket. An example of this is a PR showing as OPEN instead of CLOSED.

This is reproducible on Data Center: yes

Steps to Reproduce

1. Connect Bitbucket DC to a Jira Cloud instance
2. Create a PR with the name of a Jira ticket and ensure it can be seen in the development panel as OPEN
3. Block traffic from Bitbucket to Jira
4. Close the PR
5. Unblock traffic from Bitbucket to Jira
6. Check that the Jira ticket still shows the PR as OPEN

Expected Results

There should be a way to refresh the data via OAuth similar to how you can with Application Links to transition the PR to closed

Actual Results

The OAuth development panel shows the out of sync OPEN status

Workaround

Using an application link to connect Bitbucket DC to Jira Cloud displays the up to date information. However, this appears in a seperate development panel, it is not merged into the OAuth development panel