Automate @hypervideo/drizzle-orm publishes from beta

[danieljvdm]

Summary

• add a GitHub Actions workflow that publishes @hypervideo/drizzle-orm on pushes to beta and via manual dispatch
• compute the next -hyper.N version for whatever beta version drizzle-orm/package.json currently declares
• rewrite the packed tarball metadata so the published package is scoped to @hypervideo, points at hypervideo/drizzle-orm, and publishes to GitHub Packages

Notes

• this is beta-only; main is intentionally not part of the workflow
• hypervideo/beta currently has drizzle-orm@1.0.0-beta.18, so the first automated beta release from that branch would be 1.0.0-beta.18-hyper.0
• the effect fix we published manually today remains 1.0.0-beta.17-hyper.1
• the workflow prefers secrets.NPM_TOKEN when present and falls back to GITHUB_TOKEN

Validation

• verified the tarball rewrite helper locally against a packed @hypervideo/drizzle-orm artifact
• YAML parse check passed for .github/workflows/publish-hyper-drizzle-orm.yaml