Create the concept of a "preferred" / "default" fork
<!--IssueSummary start-->
<details>
<summary>
Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards.
</summary>
- [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=390441)
</details>
<!--IssueSummary end-->
As we now move from experiment to formalizing the GitLab community forks, see: https://gitlab.com/gitlab-community/meta we have identified an opportunity for improving UX.
If we currently try and open a project in the WebIDE (for which we are not members) the prompt is based on whether you have a personal fork (and if not, you will be prompted to create a personal fork).
We want to encourage collaboration and have everyone using the community forks. So we need a way to configure a preferred/default fork for any project/group? (and tie this in with the requirement for a "simple" access request mechanism).
/cc @stingrayza as we spoke about this, this morning :thumbsup:
issue