Transfering ownership of a repo with the option "Require issue keys in commit messages", results in the option not being editable when the target workspace doesn't have a JIRA integration

Issue Summary

Assume that you have a JIRA workspace integrated with a JIRA Cloud instance, and in one of the workspace's repos you enable the option "Require issue keys in commit messages".

If you transfer this repository to a different workspace that doesn't have an integration with JIRA, then this option remains enabled and it is not possible to deselect it.

Additionally, it is not possible to push new commits, either with or without an issue key in their message.
The error that is shown is "The commit message does not contain a valid issue key."

Steps to Reproduce

1. Integrate a Bitbucket workspace with a JIRA Cloud instance
2. Enable the option "Require issue keys in commit messages" in one of the repos owned by this workspace
3. Transfer the repository to a different workspace that doesn't have a JIRA Cloud integration
4. Accept the transfer request

Expected Results

The "Require issue keys in commit messages" option remains editable, and the user can enable/disable it.

Actual Results

The "Require issue keys in commit messages" option is not editable, it remains selected and the user cannot disable it.
Additionally, if the user tries to push to the repository, new commits are not accepted with the error "The commit message does not contain a valid issue key.", even if the commit messages contain an issue key. (I believe this is due to the fact that there are no links in this repository)

Workaround

1. If a user integrates the workspace that the repo is transferred to with the same JIRA Cloud instance, then it is possible to edit the "Require issue keys in commit messages" option.

2. As an alternative, the user can inspect the page with e.g. Developer Tools in Chrome, inspect the button, and then remove the word "disabled" from the HTML code. This will allow the user to deselect the option.