Group Image Repositories by parent project in group level container registry

Status

Some validation was done via a survey to our customers. Despite customers ranking "images nested to the project they were published to" scoring as something customers found important, we consistently see that customers overwhelmingly access the container registry via the project page. Only 5% of page views come from the group view. The numbers are visible on sisense

Context

Currently, all the Image repositories are listed one under the other:

And the 'namespace' to where they belong is repeated, we could group them and extract the namespace:

• gitlab-instance-administrators-68dc2b83/gitlab-instance-administration
  • 16235
  • 8406
  • etc

An example could be: