Protected packages: Label "protected" to package detail on group level

• Please check this box if this contribution uses AI-generated content (including content generated by GitLab Duo features) as outlined in the GitLab DCO & CLA

What does this MR do and why?

• Relates to #437928 (closed)
• The label "protected" is already included in the package detail page on project level, see !146206 (comment 1871347682)
• This MR adds this label to the group level by pushing the respective feature flag

🛠 with ❤ at Siemens

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

MR Checklist (@gerardo-navarro)

• Changelog entry added, if necessary
• Documentation created/updated via this MR
• Documentation reviewed by technical writer or follow-up review issue created
• Tests added for this feature/bug
• Tested in all supported browsers
• Conforms to the code review guidelines
• Conforms to the merge request performance guidelines
• Conforms to the style guides
• Conforms to the javascript style guides
• Conforms to the database guides

Screenshots or screen recordings

This MR just ensures that badge "protected" is shown in the package detail page.

Before	After

How to set up and validate locally

1. Go to the package registry setting of a project: http://gdk.test:3000/flightjs/Flight/-/settings/packages_and_registries
2. Create a new package protection rule with package name pattern @flightjs/npm_package_4d4b* (<= this will match seeded packages that are already in the package registry for this project)
3. Go to the package overview list on group level: http://gdk.test:3000/groups/flightjs/-/packages
4. Go the package detail page of one of the listed packages npm_package_4d4b1a18af8779a6212365b36e11af50: http://gdk.test:3000/groups/flightjs/-/packages/25
5. You should see the badge protected