Assign new package groups to feature flags

What does this MR do and why?

Describe in detail what your merge request does and why.

Context

In https://gitlab.com/gitlab-org/ci-cd/package-stage/package/-/issues/72+ we went through the restructuring of the group, and we now have two group labels: grouppackage registry and groupcontainer registry

In gitlab-org/quality/engineering-analytics/team-tasks#86 we discovered the problem dashboards were not accurate is because the feature flags were still assigned to the previous group.

Solution

In this MR we are assigning previous group::package feature flags to their corresponding new group.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

Relates https://gitlab.com/gitlab-org/ci-cd/package-stage/package/-/issues/72

config/feature_flags/development/ci_job_token_scope.yml

@@ -4,5 +4,5 @@ introduced_by_url: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/49750
 rollout_issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/300821
 milestone: '13.12'
 type: development
-group: group::package
+group: group::package registry
 default_enabled: false