ci: auto-publish releases after CI

[im10furry]

Summary

• Add automatic Release publishing after CI succeeds on master push.
• Keep existing tag-push and manual workflow_dispatch release paths working.
• For automatic releases:
  • reuse an existing semver tag on the CI commit when present
  • otherwise bump the latest vMAJOR.MINOR.PATCH tag by one patch version
  • create the tag and publish the GitHub Release in the same workflow
  • skip safely when rerun after the release already exists
• Add the new database module to CI test, vet, and build module lists.
• Expand release gates to run all module tests and vet checks before building assets.

Notes

• This intentionally does not rely on GITHUB_TOKEN pushing a tag to trigger another workflow. GitHub suppresses most workflow-triggering events created by GITHUB_TOKEN, so the tag creation and release publishing happen in one workflow run.
• After this PR is merged, the next successful CI run on master should publish the next patch release. With the current latest tag, that means v0.1.4.

Validation

• YAML parse check for .github/workflows/ci.yml and .github/workflows/release.yml
• Automatic tag calculation dry run: v0.1.3 -> v0.1.4
• go test -count=1 ./cmd/... ./internal/...
• go vet ./cmd/... ./internal/...
• all registry modules: go test -count=1 ./...
• all registry modules: go vet ./...
• go run ./cmd/scion doctor --strict
• git diff --check