Improve changeset/MR association

What does this MR do?

Improve changeset/MR association

The changelog script picked the first MR returned by the GitLab API for a given commit SHA. When another MR's branch was rebased on main, the API could return that unrelated MR first.

This filters the API response to only match MRs that target main and whose squash_commit_sha or merge_commit_sha matches the commit that introduced the changeset (as determined by @changesets/git).

See gitlab-org/gitlab!234775 (comment 3319701503) for an example of this and resulting discussion.

Verifying this locally

# Check out the commit where the `publish_npm_packages` job ran which created the bad changelog entry
# (https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/jobs/14238786245)
git checkout a57337cfeea43e58aa3a8c1bb88d80402bc0d655

yarn install

# Run the changeset version script.
# GITLAB_TOKEN must have the read_api permission.
CI_API_V4_URL=https://gitlab.com/api/v4 CI_PROJECT_ID=4456656 GITLAB_TOKEN=$GITLAB_API_ACCESS_TOKEN yarn changeset version

# Observe that the *incorrect* MR is added to the changelog.
# Note that it's a *different* wrong MR to what was originally added.
# This is because more MRs merged since then which contain that commit.
git diff packages/gitlab-ui/CHANGELOG.md

diff --git i/packages/gitlab-ui/CHANGELOG.md w/packages/gitlab-ui/CHANGELOG.md
index beae2e281..5f9674851 100644
--- i/packages/gitlab-ui/CHANGELOG.md
+++ w/packages/gitlab-ui/CHANGELOG.md
@@ -1,5 +1,11 @@
 # @gitlab/ui
 
+## 132.2.0
+
+### Minor Changes
+
+- [!5953](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/5953): Add theme tinted neutrals (`@markrian`)
+
 ## 132.1.0
 
 ### Minor Changes

# Now reset, and pull in the changes from this MR.
git checkout .
git checkout improve-mr-relationships-in-changelogs -- scripts/lib/changelog.mjs

# Run the changeset version script again.
CI_API_V4_URL=https://gitlab.com/api/v4 CI_PROJECT_ID=4456656 GITLAB_TOKEN=$GITLAB_API_ACCESS_TOKEN yarn changeset version

# Observe that the *correct* MR is added to the changelog :tada: 
git diff packages/gitlab-ui/CHANGELOG.md

diff --git i/packages/gitlab-ui/CHANGELOG.md w/packages/gitlab-ui/CHANGELOG.md
index beae2e281..3de720a20 100644
--- i/packages/gitlab-ui/CHANGELOG.md
+++ w/packages/gitlab-ui/CHANGELOG.md
@@ -1,5 +1,11 @@
 # @gitlab/ui
 
+## 132.2.0
+
+### Minor Changes
+
+- [!5894](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/5894): Add theme tinted neutrals (`@sdejonge`)
+
 ## 132.1.0
 
 ### Minor Changes

Screenshot

From the dry run job of this MR:

Integrations

• GitLab: mr_url
• CustomersDot: mr_url
• Duo UI: mr_url
• Status Page: mr_url
• Docs: mr_url
• Switchboard: 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

• The “What does this MR do?” section in the MR description is filled out, explaining the reasons for and scope of the proposed changes, per “Say why not just what”.
  • For example, if the MR is focused on usage guidelines, addressing accessibility challenges could be added in a separate MR.
• Relevant label(s) are applied to the MR.
• The MR is added to a milestone.
• Added the ~"component:*" label(s) if applicable.
• A changeset is added when this MR will do a patch, minor, or major update. More information can be found in doc/publishing-packages.md.

Components

• GitLab UI's contributing guidelines.
• If the MR changes a component's API, integration MR(s) have been opened (see integrations above).

Documentation

• If creating a new component page from scratch, it follows the page template structure.
• Content follows the GitLab Documentation Style Guide when appropriate.
• Related pages are cross-linked, where helpful. Component pages have related components and patterns defined in their Markdown front matter.
• If embedding a Figma file, it follows the Figma embed guide.
• Review requested from any GitLab designer or directly from a maintainer or trainee maintainer.
• Maintainer review follows the Pajamas UX maintainer review checklist.

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.