Remove legacy tag-triggered release workflow

[hectorcast-db]

NO_CHANGELOG=true

Summary

The secure release pipeline in databricks/secure-public-registry-releases-eng now owns the Maven Central and GitHub release for this repo. It dispatches tagging.yml (to create the tag) and package.yml (to build + sign artifacts), then does the actual publish + GH release from the secure side.

The previous in-repo tag-triggered path in release.yml is the legacy entry point that the secure pipeline has replaced. This PR removes it and keeps only the release-build dry-run that runs on every branch push.

Per-file decisions

• .github/workflows/release.yml -- edited and renamed to .github/workflows/release-build-check.yml (top-level name: Release Build Check).
  • Removed: the push.tags: ['v*'] trigger.
  • Removed: the tag-gated steps (if: startsWith(github.ref, 'refs/tags/')) -- Publish to Maven Central Repository (Deploy), Write release notes to file, Create GitHub release.
  • Removed: the !startsWith(...) guard on the dry-run step (no longer needed now that the tag trigger is gone).
  • Preserved: the branch-push trigger and the Run Release Dry-Run (Verify) step, which is what "verify the release build still works" means in this repo.
• .github/workflows/debug-prelease.yml -- not present in the repo, nothing to do.
• .github/workflows/tagging.yml -- unchanged (dispatched by the secure release pipeline).
• .github/workflows/package.yml -- unchanged (dispatched by the secure release pipeline).
• All other workflows (push.yml, conftest.yml, integration-tests.yml, external-message.yml, next-changelog.yml) -- unchanged; they are PR / merge_group CI or unrelated automation.

Heads up: required-check rename

The job name inside the renamed workflow is now constant (Run Release Dry-Run) instead of the previous dynamic name (${{ startsWith(github.ref, 'refs/tags/') && 'Publish Release' || 'Run Release Dry-Run' }}). The dry-run side produced the same Run Release Dry-Run string before, so if anything on the branch side was using that exact name as a required status check it should continue to match. If branch protection was referencing the workflow file by path (release.yml), that reference will need to be updated to release-build-check.yml.

Test plan

• Confirm this PR's own CI (build from push.yml on pull_request) runs green.
• On merge to main, confirm the renamed workflow fires on the push and the Run Release Dry-Run job succeeds.
• Confirm no tag-push events target this workflow any longer.
• Update any branch-protection required-check references from release.yml to release-build-check.yml if they existed.

[github-actions]

If integration tests don't run automatically, an authorized user can run them manually by following the instructions below:

Trigger:
go/deco-tests-run/sdk-java

Inputs:

• PR number: 775
• Commit SHA: 20d516665029b12b44931bc2c1f4f0bd3e132a1b

Checks will be approved automatically on success.