Improve the fork workflow for teams

We understand that the fork workflow can be used to create forked repositories under the team account, however, this makes the team overview/repository list very crowded.

We would like to list the forked repository in a separated list or/and by projects.

eg.

• The user "Aby" create a fork named "fork_from_A"
• She can grant access for every user that belongs to the team.
• This repository is "owned" by the "Team_A" OR "Project_A" and it's not listed in the team overview, anyway, it's accessible by the TeamA.

This would provide the user that use the forked workflow, a cleaner view of the team account and a better access control since the repositories would be managed by project and/or would not be listed in the "Main Repository" (overview) of the team.