[BITBUCKET]: Enhance Preferred Remotes for more than one remote

[jeremyfiel]

Is your feature request related to a problem? Please describe.
Preferred remotes only uses the first match, or a random match based on some other logic that I'm not aware of.

I have more than one fork I would like to fetch pull requests from because we are using the forking strategy.
https://www.atlassian.com/git/tutorials/comparing-workflows/forking-workflow#:~:text=The%20Forking%20Workflow%20helps%20a,a%20%22pull%22%20style%20workflow.

Sometimes we have a fork with a PR that needs to be approved on that fork prior to creating another PR for our main repo. I would like to manage both of these pr's in the extension.

Describe the solution you'd like
Provide a way to set more than one remote to fetch pull requests, issues and pipelines from.

Describe alternatives you've considered

Additional context

[bwieger-atlassian-com]

Hey @jeremyfiel ! Thanks for raising this feature request!

I'll keep this open so we get around to it.

At the moment, we are working on making performance much better and getting the UI cleaned up.

[ebresie]

Wouldn't adding new remote repos be better suited under repository area?

Then when creating PR it leverages selecting to/from any defined remote repository?