fix: use compiler version for standalone CLI distribution versioning

[Copilot]

@typespec/standalone-cli follows a different version scheme (0.83.0) than @typespec/compiler (1.13.0). The publish pipeline was writing the standalone package version to latest.txt and blob storage paths, while tsp --version reports the compiler version — causing Scoop/winget/Homebrew listings to show a version users never see.

Changes

• eng/tsp-core/pipelines/jobs/cli/publish-artifacts.yml: Changed workingDirectory for the version-reading step from packages/standalone → packages/compiler, so latest.txt and blob storage paths use the compiler version consistently with tsp --version output.

[timotheeguerin]

@copilot wondering if instead we should just make sure the version match at all time and add standlone cli to the same version policy

[Copilot]

@copilot wondering if instead we should just make sure the version match at all time and add standlone cli to the same version policy

Done. Moved @typespec/standalone-cli into the typespec-stable lockstep policy (commit fix: move standalone-cli to typespec-stable version policy and align version to 1.13.0), bumped its version to 1.13.0, and reverted the pipeline change since the versions now stay in sync automatically.

[microsoft-github-policy-service]

Hi @@copilot. Your PR has had no update for 14 days and it is marked as a stale PR. If it is not updated within 14 additional days, the PR will automatically be closed. If you want to refresh the PR, please remove the stale label.