Promote staging to main: fix the release job's release notes

[chrisdburr]

Summary

This brings one change from staging to main: #1004, which fixes the release job.

The release job runs only on main. It failed on 29 September while generating release notes, so v0.8.0 was deployed without a tag or changelog entry. #1004 moves conventional-changelog-conventionalcommits to ^9.3.1, the newest major that works with the writer our release-notes generator loads. Releases since 0.5.0 have had empty notes for the same reason.

What changes on main

• The preset version, in package.json and pnpm-lock.yaml (dev dependency only).
• A unit test that renders release notes from .releaserc.json with the real plugins.
• Type declarations for the two plugins used by that test.
• .releaserc.json added to the build workflow's path lists.
• A Dependabot rule that holds the preset below major 10 until the generator moves to writer 9.

No application code changes. The production app is rebuilt and restarted as usual when this merges.

Expected after merge

The Release workflow should tag v0.8.0, add a 0.8.0 entry with sections to CHANGELOG.md, publish a GitHub release with the same notes, and merge main back into staging.

Checks

#1004's CI and the staging build and deploy of its merge commit both passed.

[github-actions]

promotion PR — structural quality was gated per feature PR on staging