Some packageregistry endpoints still rate-limited
Doing the analysis on https://gitlab.com/gitlab-com/gl-infra/scalability/-/issues/749, we found that some users are downloading nuget package metadata using the /api/:version/groups/:id/packages/nuget/metadata/*package_name/index
route that will be rate-limited when we enforce.
This doesn't match our current path patterns because the need to have a /-/ after /groups/. We should find out if:
- this is just one user or many, and
- if
- the path is incorrect (working by co-incidence?) and they should be including /-/, or
- we've missed a path form in the regex.