docs(releasing): Homebrew tap step + npm --access public in the release checklist

[oratis]

Finishes the release process so no channel drifts again (Homebrew had silently fallen behind to 0.9.0). Pure docs — no code.

docs/RELEASING.md

• Step 5 fixed: npm publish → npm publish --access public — the scoped package (@oratis/lisa) defaults to restricted, so without the flag npm 404s on the PUT (the exact error hit while shipping v0.11.0).
• New step 6 — Homebrew tap bump: gh workflow run "Release — Homebrew tap" after npm publish, with a pointer to the one-time HOMEBREW_TAP_TOKEN setup in PUBLISH.md §2.
• Workflows table updated to four entries and split by trigger (two tag-triggered; npm publish + Homebrew are manual, post-tag) — the old "all three, all tag-triggered" line was no longer accurate.

Context

The Homebrew automation itself (.github/workflows/release-homebrew.yml) + the PUBLISH.md §2 setup already landed on main; this PR just adds the matching one-line checklist entry so RELEASING.md reflects the full four-channel flow:

npm version  →  push tag (auto: DMG + bundles)  →  npm publish --access public  →  gh workflow run "Release — Homebrew tap"

🤖 Generated with Claude Code