Automatically create changeset file for SVG changes

The gitlab-org/gitlab-svgs> project had automation which automatically created releases of @gitlab/svgs when SVG files changed.

With this project using Changesets, releases need to be deliberately triggered.

There's already been at least one case where a release wasn't created: !5316 (comment 2918499986).

Proposals

One or more of these could work. The feedback was As much automation as possible would be beneficial.

Create a lefthook pre-commit hook that generates the changeset file(s) that describe the SVG changes.

Have a job in main that adds the changeset(s) Just In Time. One downside of this is that the changeset file(s) won't be reviewable.

Have a job that fails in MRs if there are SVG changes but no changeset files.

Add a danger comment that asks whether a changeset file should be added.