ci(DCP-2583): build in create-release workflow

[dessskris]

This pull request refactors and simplifies the release automation workflow, moving from a PR-title-based trigger ([run-release]) to a label-based trigger (release). It consolidates and streamlines CI gates, updates documentation to match the new process, and merges the build and release steps for improved reliability and clarity.

Release workflow improvements:

• The release process is now triggered by applying the release label to a PR, rather than adding [run-release] to the PR title. This change is reflected in both workflow files and documentation. [1] [2] [3] [4] [5] [6]
• The release-tag-gate.yml and release.yml workflows have been removed, consolidating checks and builds into a single streamlined process. [1] [2]

CI gate and workflow changes:

• The changelog-gate.yml workflow now checks for the release label instead of [run-release] in the PR title, and only fails if the label is present but CHANGELOG.md is not modified. [1] [2]
• The create-release.yml workflow now runs on pushes to main, checks merged PRs for the release label, creates a tag and GitHub Release, and immediately builds and uploads binaries for all platforms. [1] [2] [3]

Documentation updates:

• All instructions in DEVELOPMENT.md and README.md now reference the release label workflow, removing references to [run-release] in PR titles and the old validation gates. [1] [2] [3]
• Minor improvements to markdown formatting, links, and quick reference tables for clarity and consistency. [1] [2] [3] [4] [5] [6] [7] [8]

Summary of most important changes:

Release workflow and CI changes:

• Switch release trigger from [run-release] PR title tag to release label; update all workflows and documentation accordingly. [1] [2] [3] [4]
• Remove obsolete release-tag-gate.yml and release.yml workflows, consolidating checks and builds into create-release.yml. [1] [2]
• Update changelog-gate.yml to check for the release label and require CHANGELOG.md modification only when the label is present.

Build and release process:

• In create-release.yml, add a job to check merged PRs for the release label, then create a tag, GitHub Release, and build/upload binaries for all platforms in one workflow. [1] [2] [3]

Documentation and developer experience:

• Update DEVELOPMENT.md and README.md to describe the new label-based release process, improve formatting, and fix links. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11]

[prolific-snyk]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[Copilot]

Pull request overview

This PR consolidates release creation and binary build/upload into a single GitHub Actions workflow (create-release.yml) by deleting the standalone release.yml workflow and adding a new build job that runs after release finalization.

Changes:

• Removed .github/workflows/release.yml and migrated its build/upload logic into create-release.yml.
• Added a build job that checks out the newly created tag and uploads multi-platform binaries to the GitHub release.
• Updated actions/setup-go usage in the workflow to v6.4.0 and wired the release tag as a job output.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
.github/workflows/release.yml	Deleted legacy workflow that built/uploaded release binaries on release.published.
.github/workflows/create-release.yml	Added tag output + new build job to build/upload binaries as part of the release creation pipeline.

[script-this]

Purely cosmetic but won't interpret these as newlines in bash I don't think.