Include compile-production-assets and build-assets-image job on mirror push pipelines

What does this MR do and why?

When creating internal packages, a commit must be propagated from the GitLab security to the GitLab dev repository via mirroring. Because of the mirror, a shorter pipeline (sync stage) is triggered on the dev stable branch (example). Currently, this stable branch sync pipeline doesn't include the build-assets-image job that is required to build the internal package.

As a workaround, we added a service that triggers another pipeline. This has the downside of spending pipeline resources to wait for just one job. Since we only need the build-assets-image job for the internal releases, this MR updates the CI rules to include it with its dependency compile-production-assets job on mirror sync push pipeline.

Testing

1. I pushed my changes to the 42-2-stable-ee branch that we use for testing internal releases in the Security mirror: https://dev.gitlab.org/gitlab/gitlab-ee/-/commit/d6388ca535e1c47e95bf08b5d2dbb9ac2d9e394e
2. I pushed an empty commit to the same test branch and wait for this commit to be mirrored to dev.
   • It triggers this pipeline https://dev.gitlab.org/gitlab/gitlab-ee/-/pipelines/367318. This pipeline contains the build-assets-image and compile-production-assets jobs with the jobs on sync stage.
3. I pushed a commit with a change to the VERSION file which mimics the version update that we do in the internal release.
   • It triggers this pipeline https://dev.gitlab.org/gitlab/gitlab-ee/-/pipelines/367323. This pipeline contains the build-assets-image and compile-production-assets jobs with the jobs on sync stage.

References

Please include cross links to any resources that are relevant to this MR. This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.

• gitlab-com/gl-infra/delivery#20876 (closed)

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.

Screenshots or screen recordings

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

Before	After

How to set up and validate locally

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