Issue Summary

Only the pull request author can manually start a Rovo Dev code review in Bitbucket Cloud. Other users still see the Review code button in the Rovo Dev panel, including reviewers and repository admins with write access. When they click it, they get the generic error "Code review failed. Something went wrong and Rovo Dev couldn't review this pull request." The error doesn't say why the review can't run.

Steps to Reproduce

1. Enable Rovo Dev code reviews on a repository, with the trigger set to Only when pull request is created.
2. User A opens a pull request. Rovo Dev reviews it automatically.
3. User A pushes new commits. The Rovo Dev panel shows "Code changes detected – Review code again for potential improvements?"
4. User B, a reviewer or repository admin who isn't the author, clicks Review code.

Expected Results

• Users with the right repository permissions can start a manual review, for example when the author is unavailable. Credits can still come from the author's allocation.
• Until that's possible, non-authors don't see the Review code button, or they get a clear message that only the author can start a manual review.

Actual Results

• The Review code button is shown to non-authors.
• Clicking it fails with the generic error.
• No review runs until the author is available.

Use case

When the PR author is on leave, teammates can't get an updated Rovo Dev review on new commits. Switching the repository to review on each commit isn't always acceptable, because of credit usage and review noise.

Workaround

Wait for the PR author to click Review code, or have a repository admin change the trigger setting to When pull request is created and on each commit. That setting applies to the whole repository.