Use .tool-versions file to sync local dev and github actions

[djeebus]

This way a version bump in the .tool-versions file is automatically used in tests, linters, releases, and local dev. It also helps make it clear which version we expect people to use locally.

---

Note

Add .tool-versions and update GitHub Actions to parse and use its values for pnpm, Node.js, Python, Poetry, and Deno.

• CI Workflows:
  • Add parsing of .tool-versions via wistia/[email protected] in cli_tests.yml, generated_files.yml, js_sdk_tests.yml, lint.yml, publish_packages.yml, python_sdk_tests.yml, release.yml, release_candidates.yml.
  • Replace hardcoded versions with ${{ env.TOOL_VERSION_* }}:
    • pnpm: TOOL_VERSION_PNPM
    • node-version: TOOL_VERSION_NODEJS
    • python-version: TOOL_VERSION_PYTHON
    • poetry installer version: TOOL_VERSION_POETRY
    • deno-version: TOOL_VERSION_DENO
• Tooling:
  • Add .tool-versions specifying deno 1.46.3, nodejs 20.19.5, pnpm 9.15.5, python 3.9, poetry 1.8.3.

^{Written by Cursor Bugbot for commit 358b62f. This will update automatically on new commits. Configure here.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 358b62f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR