Internal release - Expand internal release service to trigger CNG pipeline

Context

To remediate GiLab Dedicated instances within remediation SLAs, release managers need to build and deliver a private package to such instances without disclosing the vulnerability and starting a patch.

On #20644 (closed), release tooling was expanded with a barebone service to handle the internal release process. The internal release process will use a tagless approach to build the private packages, one of the steps for the tagless approach is to trigger a CNG pipeline

Proposal: Expand the internal release service to trigger a CNG pipeline

The internal release service, to be introduced by #20644 (closed) should be expanded to trigger a CNG pipeline.

Considerations:

1. The CNG pipeline should be triggered after the VERSIONs file have been updated on the security stable branches #20644 (closed)
2. A CNG pipeline should be triggered per applicable versions (N-1 and N-2) - #20645 (closed)
3. CNG pipeline should be triggered on dev (To be confirmed)
4. Investigation will be required to understand the environment variables to be passed to the pipeline, details https://gitlab.com/gitlab-com/gl-infra/delivery/-/issues/20565#procedure-to-build-a-tagless-internal-package and https://gitlab.com/gitlab-com/gl-infra/delivery/-/issues/20565#note_2139886131