Add Stabilize-Release.ps1 script for release process

[rainersigwald]

Add a script to automate creating commits like 6e61e96.

[Copilot]

Pull request overview

This PR adds automation for the MSBuild release stabilization process by introducing a PowerShell script that modifies versioning properties in eng/Versions.props. The script replaces a manual process previously documented in the release checklist.

Changes:

• Adds scripts/Stabilize-Release.ps1 to automate adding DotNetFinalVersionKind and changing PreReleaseVersionLabel during release stabilization
• Updates documentation/release.md to reference the new automation script
• Updates documentation/release-checklist.md to instruct maintainers to use the script instead of manual editing

Reviewed changes

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

File	Description
scripts/Stabilize-Release.ps1	New PowerShell script that automates the release stabilization process by modifying eng/Versions.props
documentation/release.md	Adds documentation about the new Stabilize-Release.ps1 script
documentation/release-checklist.md	Updates final branding checklist step to use the new automation script

[Copilot]

The error message says "Please run this script from the repository root or scripts directory" but the script only supports being run from the repository root or scripts directory. The current logic finds the repo root correctly regardless of where it's run from (as long as the file exists), so the error message could be more accurate, such as "Could not find eng/Versions.props at expected location. Repository structure may have changed."

Suggested change

	Write-Error "Could not find eng/Versions.props. Please run this script from the repository root or scripts directory."
	Write-Error "Could not find eng/Versions.props at expected location: '$versionsPropsPath'. Repository structure may have changed."