ci: add GAR publish workflow on templ-for-bwa and remove manual publish script

[braines-blw]

Summary

Replaces the manual ./publish GitHub Packages script with a tag-triggered CI workflow that publishes the five @blue-water-autonomy/html-eslint-* packages to Google Artifact Registry (us-central1-npm.pkg.dev/blue-water-autonomy-operations/bwa-npm) via direct Workload Identity Federation — no service account, no long-lived credentials.

Base branch: targets templ-for-bwa, not main. Only templ-for-bwa carries the five BWA-scope package renames; a publish off main would push the wrong upstream tree.

Changes (exactly the ticket scope — 2 files)

• Add .github/workflows/release.yml ("Publish to GAR"): push: tags: ['bwa-v*'] + workflow_dispatch (optional bump); checkout@v4 at ref: ${{ github.ref }}/fetch-depth: 0; google-github-actions/auth@v2 against provider github-oidc-bwa-npm, no service_account:; yarn lerna publish --no-private --no-push --no-git-tag-version --yes, auto-selecting from-package vs prerelease --preid bwa.
• Delete the manual root ./publish script.

The workflow body matches the AI-917 spec; it is Prettier-formatted to satisfy the repo's check:format gate. The only formatting deltas are a double-quoted tag glob (["bwa-v*"]) and single-space-before-inline-comment — no semantic change to the trigger or any step.

Process artifacts (.agentic/specs, .agentic/summaries) were intentionally excluded from this PR — they are implement-pipeline bookkeeping, not part of AI-917's deliverable, and don't belong in this upstream-tracking fork.

CI status / known pre-existing failure

• Validate PR title and Check Format failures were caused by this PR's earlier title/formatting and are fixed here (conventional-commit title; Prettier-clean workflow).
• Integration Test fails for a reason independent of and pre-existing to this PR: packages/integration-test's makePackageJson wires file: overrides for html-eslint-plugin/-parser/-template-parser/-template-syntax-parser but not @blue-water-autonomy/html-eslint-types, so the fixture yarn install resolves it from public npm and fails YN0035: @blue-water-autonomy/html-eslint-types@npm:^0.54.0: Package not found (these packages are unpublished — the exact chicken-and-egg AI-917 exists to break). This PR's diff touches zero code/package/dep files, and main.yml only runs CI on push-to-main or PRs, so this is the first CI ever executed against templ-for-bwa; the failure exists on templ-for-bwa HEAD regardless of this PR. Reconciling the fork is explicitly out of AI-917 scope; tracked separately.

Post-merge operational verification (maintainer)

1. On templ-for-bwa HEAD: git tag bwa-v0.54.2 && git push origin bwa-v0.54.2; confirm the run is green.
2. gcloud artifacts versions list --repository=bwa-npm --location=us-central1 --project=blue-water-autonomy-operations --package=html-eslint-parser (and the other 4) shows the version.
3. Confirm power-module's npm install (AI-918) resolves all 5 from GAR.

Linear: AI-917

🤖 Generated with Claude Code