This reverts commit c4df25a.

…eous cache generation (#8333)

Couple things going on here to unpack:
- this reverts #8204
- b/c that was reverted our CI times went from 4/5 min back to 8min
because we had to recompile things during setup.yml in the `yarn` step.
this was adding ~2min back to each CI action.
- we were hitting our 10GB limit before but the majority of that was
because we were adding `-${{github.sha}}` to a bunch of our tooling
caches, creating a bunch of extra cache entries for no reason

Fixes:
- removes the `${{github.sha}}` from the key, unnecessary.
- caches `node_modules` again to save CI time again
- I increased our org cache limit to 20GB for now, we only pay for
actual usage, things get auto-purged after 7 days anyway
<img width="476" height="137" alt="Screenshot 2026-03-24 at 14 26 19"
src="https://github.com/user-attachments/assets/8ddfa763-554a-4270-a832-69628f23fa6f"
/>

- i'll manually clear some cache entries as well

#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    |