chore: make @tevm/contract production ready

[roninjin10]

Summary

• harden CI and Changesets release checks, validate package exports with publint and Are the Types Wrong, and use npm OIDC provenance publishing
• add broad prebuilt-contract coverage and fix missing runtime functionName metadata on read/write action creators
• upgrade Vocs to 2.7.2, make missing Vercel configuration fail loudly, and improve source JSDoc, generated API docs, and ecosystem guidance

Validation

• Node 24.18.0 / pnpm 9.15.9 frozen install
• pnpm lint
• pnpm typecheck
• pnpm build
• pnpm check:package
• pnpm test:coverage: 5 files, 36 tests, 100% statements/branches/functions/lines
• pnpm run docs
• pnpm docs:build: Vocs generated 39 static files
• pnpm exec changeset status
• actionlint
• git diff --check

Release and deployment setup

• Before merging the existing 1.0.0 Changesets release PR, configure the npm trusted publisher for evmts/tevm-contract and workflow release.yml; the workflow intentionally has no npm token fallback.
• Configure the docs GitHub environment with VERCEL_ORG_ID, VERCEL_PROJECT_ID, and VERCEL_TOKEN, link the site project to contract.tevm.sh, and re-run Docs. The current domain returns Vercel DEPLOYMENT_NOT_FOUND.

Risks

• @tevm/utils remains a published compatibility dependency at ^1.0.0-next.148 until migration to Voltaire; no standalone tevm-utils repository is introduced.
• Publishing and production deployment are intentionally not performed by this PR.