Automate v1 releases after successful main CI

[jakthom]

Summary

• Mirrors the proven open-ships/n2k post-CI release workflow.
• Adds VERSION with the deliberate 1.0.0 release baseline.
• After successful CI on the current main commit, creates and pushes the semantic-version tag and publishes a generated GitHub Release.
• Skips superseded CI runs and commits that are already tagged.
• Increments patch releases automatically until VERSION is raised to a newer baseline.
• Makes the lossless-subscription overflow test deterministic after hosted race CI exposed its startup timing assumption.

Validation

• Release workflow and VERSION match the active n2k automation.
• Repository Actions are enabled with write-capable GITHUB_TOKEN permissions.
• Teleop has no existing local or remote release tags, so the first selected tag is v1.0.0.
• Focused overflow test passed 1,000 race-detector repetitions.
• go test ./...
• CGO_ENABLED=0 go test ./...
• go test -race ./...
• go vet ./...
• Hosted CI passed on Ubuntu, macOS, and Windows for the same tree before the clean follow-up branch was created.

Release behavior

Merging this PR starts CI on main. If that run succeeds and its commit is still current, the release workflow creates v1.0.0 and publishes the GitHub Release automatically.