Sync eng/common directory with azure-sdk-tools for PR 13750

[azure-sdk]

Sync eng/common directory with azure-sdk-tools for PR Azure/azure-sdk-tools#13750 See eng/common workflow

[Copilot]

Pull request overview

This PR syncs the eng/common infrastructure with updates from azure-sdk-tools PR 13750, switching release-plan completion handling to use the azsdk CLI and wiring in a reusable installer template.

Changes:

• Update Mark-ReleasePlanCompletion.ps1 to call the azsdk CLI to mark release status, removing direct DevOps work item helper usage and adding validation for the CLI path.
• Extend the mark-release-completion pipeline template to install the azsdk CLI via a new install-azsdk-cli.yml step and pass its path into the script.
• Introduce install-azsdk-cli.yml, a shared template that installs the Azure SDK tools CLI using the azure-sdk-mcp.ps1 helper.

Reviewed changes

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

File	Description
eng/common/scripts/Mark-ReleasePlanCompletion.ps1	Switches release-plan status updates to use the azsdk CLI and adds parameterization/validation for the CLI path.
eng/common/pipelines/templates/steps/mark-release-completion.yml	Ensures the azsdk CLI is installed before running the release completion script and passes the CLI path into it.
eng/common/pipelines/templates/steps/install-azsdk-cli.yml	Provides a reusable pipeline step to install the azsdk CLI via the MCP installer script.

[Copilot]

The -AzsdkExePath '$(Agent.TempDirectory)/azsdk' argument assumes the CLI executable is named azsdk without an extension, but on Windows the installer script (azure-sdk-mcp.ps1 via AzSdkTool-Helpers.ps1) produces azsdk.exe. If this template is ever run on a Windows agent, the path passed to Mark-ReleasePlanCompletion.ps1 will not exist, causing its initial Test-Path check to fail and the step to error even though the tool is installed. To make this robust, either adjust the path to include the .exe suffix on Windows or update the script to handle extension normalization so the same template can run cross-platform.

Suggested change

	-PackageInfoFilePath '${{ parameters.ConfigFileDir }}/${{ parameters.PackageArtifactName }}.json' -AzsdkExePath '$(Agent.TempDirectory)/azsdk'
	-PackageInfoFilePath '${{ parameters.ConfigFileDir }}/${{ parameters.PackageArtifactName }}.json' -AzsdkExePath '$(Agent.TempDirectory)/azsdk${{ if eq(variables['Agent.OS'], 'Windows_NT') }}.exe${{ end }}'

[Copilot]

On Windows agents, azure-sdk-mcp.ps1 installs the CLI as azsdk.exe (see Helpers/AzSdkTool-Helpers.ps1 where the Windows executable is $Package.exe), but this script expects -AzsdkExePath to point to a path without an extension and then validates it with Test-Path. If the pipeline passes a value like $(Agent.TempDirectory)/azsdk (as in the updated template), Test-Path will fail on Windows even though azsdk.exe exists, causing the script to error out unnecessarily. Consider normalizing the path here (e.g., appending .exe on Windows when the extension is missing) so the script works consistently across platforms.