Tweak changeset format in docs to match tool

[CraigMacomber]

Description

Fix examples in changeset docs to match whats generated by our tool line spacing wise so we don't get needless diffs when having AI review changesets based on those examples.

Reviewer Guidance

The review process is outlined on this wiki page.

[Copilot]

Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.

[github-actions]

Hi! Thank you for opening this PR. Want me to review it?

Based on the diff (6 lines, 1 files), I've queued these reviewers:

• Correctness — logic errors, race conditions, lifecycle issues
• Security — vulnerabilities, secret exposure, injection
• API Compatibility — breaking changes, release tags, type design
• Performance — algorithmic regressions, memory leaks
• Testing — coverage gaps, hollow tests

How this works

• Adjust the reviewer set by ticking/unticking boxes above. Reviewer toggles alone don't trigger anything.

• Tick Start review below to dispatch the review fleet.

• After review finishes, tick Start review again to request another run — it auto-resets after each dispatch.

• This comment updates as new commits land; your reviewer selections are preserved.

• Start review

[github-actions]

Bundle size comparison

Base commit: 7c3fc51d5d204a16299014921e93d522590a4af2
Head commit: b8f0845759bd084305b1e6ae18c3ca9a4ba0ccea

⚠️ Comparison unavailable.

No CI build was found for the PR HEAD commit. This shouldn't happen — the workflow only runs after the PR's Build - client packages check completes. Please report.