Add in dynamic version for telemetry using GITHUB_ACTION_REF

[MaddyMicrosoft]

Summary

Reports the action ref the consumer actually pinned in telemetry, instead of a hardcoded version string. Prevents manual changes and drift.

Change

setUserAgent built the AZURE_HTTP_USER_AGENT / AZUREPS_HOST_ENVIRONMENT strings with a hardcoded @v3. Because it was hardcoded, it silently goes stale across major bumps (the same class of bug that currently has the CLI action still reporting @v2 on its v3 release).

This reads GITHUB_ACTION_REF (set by the runner to the ref the workflow pinned, e.g. v3, v3.1.0, a SHA, or main) and uses it in the user-agent, falling back to unknown when it is not set:

let actionRef = process.env.GITHUB_ACTION_REF || 'unknown';
... `GITHUBACTIONS/${actionName}@${actionRef}_...`

• fixed action concurrency lock

Why

• The version string can no longer go stale on a major bump; it always reflects the real ref.
• It is more accurate telemetry: it distinguishes consumers pinned to a major (@v3) from an exact version, a SHA, or main.

Notes

• Behavior change for telemetry consumers: the value after @ is now the pinned ref rather than always @v3, so downstream parsing that assumed @vN should bucket the new values. Worth a heads-up to whoever owns the user-agent dashboards.