fix: add explicit permissions to TypeScript SDK test workflow

[adnanrhussain]

Summary

• Resolves code scanning alerts #1 – #5 - workflow was relying on default repository permissions instead of declaring explicit
  least-privilege permissions
• Rather than granting actions: write (which styfle/cancel-workflow-action requires), we replaced it with native concurrency — keeping the final permission scope to contents: read only

[Copilot]

Pull request overview

This PR addresses a GitHub code scanning alert by explicitly declaring least-privilege GITHUB_TOKEN permissions for the TypeScript SDK test workflow, rather than relying on repository defaults.

Changes:

• Add an explicit top-level permissions block to the TypeScript SDK CI workflow.
• Grant contents: read (for checkout) and actions: write (to support cancelling prior runs).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

This repo’s other workflows set permissions at the job level (e.g. .github/workflows/publish-typescript-sdk.yml:11, release-please.yml:10, conventional-commits.yml:16). To stay consistent and keep future least-privilege tighter, consider moving this workflow-level permissions block down into each job (or only jobs that require elevated scopes).

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!