In order to publish the v4.5.0 release notes and record the v4.4.1
patch, this PR archives release notes and resets `next.mdx` for the next
cycle.

**v4.5.0.mdx** (new file):
- Archived from `next.mdx` with full frontmatter, keywords, and GitHub
release link
- Featured sections: click-through on transparent image pixels (#7942),
breaking `EmbedShapeUtil.configure()` change (#8034)
- API changes: `Editor.getResizeScaleFactor()` (#8042),
`TLImageAsset.pixelRatio` (#8163), `sanitizeSvg` (#7896),
`experimental__onDropOnCanvas` (#7911), enum-to-const refactoring
(#8084)
- 6 improvements and 20 bug fixes from production

**v4.4.0.mdx:**
- Add v4.4.1 patch release section with tooltip positioning fix (#8171)
- Add v4.4.1 to keywords

**next.mdx:**
- Reset with `last_version: v4.5.0` and empty content

### Change type

- [x] `other`

### Code changes

| Section       | LOC change    |
| ------------- | ------------- |
| Documentation | +128 / -107   |

#8276)

In order to stop docs-only hotfixes from triggering unwanted npm patch
releases, this PR adds `yarn refresh-assets --force` before the
`getAnyPackageDiff()` check in `publish-patch.ts`.

### Root cause

PR #8204 added `.yarn/install-state.gz` to the CI cache. When Yarn
determines that the install state hasn't changed (e.g. `node_modules` is
already populated and no dependencies changed), it [skips lifecycle
scripts](https://yarnpkg.com/advanced/lifecycle-scripts) including
`postinstall` ([related
discussion](yarnpkg/berry#5924)). This
means the `postinstall` hook (`husky install && yarn refresh-assets`)
never runs.

Without `refresh-assets`, the gitignored asset directories in
`@tldraw/assets` (`embed-icons/`, `fonts/`, `icons/`, `translations/`)
don't exist on disk. The `getAnyPackageDiff()` guard runs `yarn pack`
which produces a tarball missing these dirs (14 files), while the
npm-published tarball has them (265 files) — always finding a diff,
always publishing.

**Before #8204 (working):** PR #8102 docs hotfix cherry-picked to v4.4.x
— publish-patch skipped correctly, no version bump.

**After #8204 (broken):** PRs #8263 and #8270 docs hotfixes
cherry-picked to v4.5.x — both triggered unwanted npm publishes (v4.5.1
and v4.5.2).

### Why this approach

Considered three options:
1. **Remove `install-state.gz` from cache** — doesn't actually help;
Yarn skips postinstall based on dependency changes, not just the state
file
2. **Add `refresh-assets` to the setup action** — overkill; lazyrepo
already auto-runs it as a dependency of `build`, `build-types`, and
`dev`
3. **Add `refresh-assets` to `publish-patch.ts`** — targeted fix
matching what `trigger-sdk-hotfix.ts` already does (line 98)

Option 3 is the right call. `publish-patch.ts` is the only workflow
confirmed broken — everything else is protected by either lazyrepo's
dependency graph or explicit `refresh-assets` calls in the workflow
YAML.

### Change type

- [x] `bugfix`

### Test plan

Verified locally:
1. Removed asset dirs to simulate CI with warm cache (no postinstall)
2. `yarn pack` on `@tldraw/assets` → 14 files
3. Ran `yarn refresh-assets --force`
4. `yarn pack` again → 265 files

On a release branch with only docs changes, `getAnyPackageDiff()` should
now return `null` → "No packages have changed, skipping release" → no
publish.

### Code changes

| Section        | LOC change |
| -------------- | ---------- |
| Config/tooling | +4 / -0    |