Update ci_job_token_scope feature flag group to container registry

🍰 Context

A few milestones ago, the Package stage was split into two teams:

1. groupcontainer registry
2. grouppackage registry

ci_job_token_scope is a feature flag with a rollout issue here: #300821 (closed).

This feature flag controls Container Registry repositories access with a CI job token.

Obviously, this feature flag is part of the groupcontainer registry.

That's not what the feature flag file is saying. This MR fixes that.

This brings issues in automated reporting on feature flag s. See gitlab-org/quality/triage-reports#10553 (comment 1251918958).

🔍 What does this MR do and why?

• Update config/feature_flags/development/ci_job_token_scope.yml group to groupcontainer registry

📺 Screenshots or screen recordings

None

⚙ How to set up and validate locally

n/a

☑ 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.