chore: GH action to remind developers to add release notes in CHANGELOG.md

[cryptodev-2s]

Explanation

This PR introduces a new CI workflow that enforces the inclusion of a CHANGELOG entry for any changes made by developers. It supports both single-package repositories and monorepos using Yarn workspaces.

The shared workflow has been structured for easy migration to the github-tools repository in the future.

Testing flow:

1. The first commit runs the workflow and passes, as it doesn’t introduce any changes that require a changelog update.
2. The second commit adds a dummy change to the ens-controller package, triggering the requirement for a changelog entry in ens-controller/CHANGELOG.md.
3. The third commit fixes the pipeline by adding the missing changelog entry for the ens-controller package.
4. The fourth commit introduces dummy changes in two packages — accounts-controller and address-book-controller — both of which require corresponding changelog entries.
5. The fifth commit resolves the pipeline by adding the necessary changelog entries for both accounts-controller and address-book-controller.

Fixes: https://github.com/MetaMask/MetaMask-planning/issues/3678

References

Changelog

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed, highlighting breaking changes as necessary
• I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes

[cryptodev-2s]

This file is intended to be moved to the github-tools repository later.

[cryptodev-2s]

This script is intended to be moved to the github-tools repository later.

[cryptodev-2s]

Dummy change that should trigger the workflow