VNext/changes to gha workflows

[gimlichael]

This pull request introduces a manual .NET Prerelease Flow for publishing signed NuGet Preview and Release Candidate packages from long-lived development branches. Tagged branch commits are verified and published as the same validated Release artifact, while main-only release tags keep their existing behavior.

Prerelease publishing:

• Adds a manually triggered workflow that requires an existing SemVer prerelease tag at the selected branch tip before verification starts.
• Publishes the already verified Release package artifact to the protected Production environment without rebuilding packages.
• Excludes branch prerelease tags from the main release workflow so they never start the main-only release flow.

Shared verification:

• Lets the shared verification pipeline run for prerelease branches with the expected version, branch-scoped SonarCloud analysis, and Codecov reporting.

Documentation:

• Documents when to use the prerelease flow, the tagging steps, and the Production deployment branch rules it depends on.

[greptile-apps]

Confidence Score: 5/5

[Critical impact] The PR appears safe to merge; no actionable issues were established.

Summary

Adds manual prerelease publication from tagged development branches.

• Tagged development branches can publish prerelease packages through a manual workflow.
• Shared verification checks prerelease branches under their own identity.

No actionable issues were established. Verification was based on the workflow definitions; no Actions runs were executed.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[Manual development branch run] --> B[Check triggering commit and prerelease tag]
  B --> C[Shared build, tests, and analysis]
  C --> D[Verification-NuGet-Release artifact]
  D --> E[Check package versions and existing NuGet content]
  E --> F[Protected Production publication]
  D --> F

Loading

_{Reviews (1) · Last reviewed commit: "📝 document branch prerelease publicatio..." · Reviewed by Greptile}