ci: Add a job to update deployments

What does this MR do?

ci: Add a job to update deployments

Similiar to the GitLab main project, we can utilize the Deployments API to create deployments when certain @gitlab/ui SHAs make it to "production". What this means in our case:

1. Merge Requests being merged into gitlab-org/gitlab. We can simply check this regularly on a schedule and parse the yarn.lock file.
2. NPM package registry, we can check the npm registry for the latest version and update accordingly.

This has the benefit, that both environments will show up in merge requests and this means an easy way for people to check their own MRs post-merge.

See also:

• https://docs.gitlab.com/ee/user/project/merge_requests/widgets.html#post-merge-pipeline-status
• https://docs.gitlab.com/ee/ci/environments/index.html#track-newly-included-merge-requests-per-deployment

Screenshots or screen recordings

In the deployments section of a merged MR:

Integration merge requests

• GitLab: mr_url
• CustomersDot: mr_url
• Status Page: mr_url

Does this MR meet the acceptance criteria?

This checklist encourages the authors, reviewers, and maintainers of merge requests (MRs) to confirm changes were analyzed for conformity with the project's guidelines, security and accessibility.

Toggle the acceptance checklist

Conformity

• Code review guidelines.
• GitLab UI's contributing guidelines.
• If it changes a Pajamas-compliant component's look & feel, the MR has been reviewed by a UX designer.
• If it changes GitLab UI's documentation guidelines, the MR has been reviewed by a Technical Writer.
• If the MR changes a component's API, integration MR(s) have been opened (see integration merge requests above).
• Added the ~"component:*" label(s) if applicable.

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• Security reports checked/validated by a reviewer from the AppSec team

Accessibility

If this MR adds or modifies a component, take a few moments to review the following:

• All actions and functionality can be done with a keyboard.
• Links, buttons, and controls have a visible focus state.
• All content is presented in text or with a text equivalent. For example, alt text for SVG, or aria-label for icons that have meaning or perform actions.
• Changes in a component’s state are announced by a screen reader. For example, changing aria-expanded="false" to aria-expanded="true" when an accordion is expanded.
• Color combinations have sufficient contrast.