[feature request]: Allow specific repositories to create issue branch on fork even when you have push access

This is in regards to the issue window. When looking at an issue on the side panel, there is an option to "Start Working on an Issue..." when you click on the arrow next to the issue:

If you don't have push access to the issue, you will receive a dialog prompt to open the issue branch on a fork on the repository; however, if you do have push access, you don't receive that option. This feature request is to make that fork option still a possibility if you have push access.

Desired workflow:

1. Open repository that you have push access to in vscode with the GitHub extension installed.
2. Find issue you want to work on is the issues window
3. Click "Start Work on Issue..." next to issue
4. Issue branch is created on forked repository where you can start work.

Actual workflow:
Step 4 in previous workflow creates issue branch on the repository you are looking at

Start in the issue window flow behind “Start Working on an Issue...” and compare the behavior when the user has push access with the fork prompt behavior. Done means users with push access can choose to create the issue branch on a fork, while the existing direct-repository workflow remains available.