Bump all SDKs and CLI to 0.26.0

[etbyrd]

Summary

Cuts a 0.26.0 release across all four packages: `@primitivedotdev/sdk`, `@primitivedotdev/cli`, `primitivedotdev` (Python), and the Go SDK.

Reason for a minor bump (not patch): the CLI ships three substantive additive features in this release.

• Auto-detect of `HTTP(S)_PROXY` at CLI startup so users behind a proxy no longer need to prefix every command with `NODE_USE_ENV_PROXY=1` (PR Auto-detect HTTP(S)_PROXY at CLI startup #79).
• `endpoints:test-endpoint` now prints a redirect when invoked on a function-kind endpoint, pointing the caller at `functions:test-function` instead of a bare `not_found` (PR Redirect endpoints:test-endpoint to functions:test-function for function endpoints #77).
• The `functions:init` scaffolder now emits a loop-protection helper (`isLoop(event)`) in the generated handler, with an early-return in the dispatcher (PR Add isLoop helper to functions:init scaffolded handler #80).

The cross-language SDKs (`sdk-node`, `sdk-python`, `sdk-go`) carry the function-deploy handler-contract docstring correction from PR #81 (no API surface change; documentation only).

Coordination note

Following the convention established in #69 and #70: this PR bumps the four packages' own versions and `CLI_VERSION_RANGE` (the scaffolded devDeps range, gated by the lockstep test). It does NOT bump `cli-node`'s `@primitivedotdev/sdk` dependency range or `SDK_VERSION_RANGE` from `^0.25.0` to `^0.26.0`; those land in a follow-up PR once `@primitivedotdev/sdk@0.26.0` is published, mirroring the #69 to #70 sequence.

Test plan

• `pnpm --filter @primitivedotdev/sdk test` (711 passed)
• `pnpm --dir cli-node exec vitest run tests/oclif/functions-init.test.ts` (27 passed, including the lockstep test that gates `CLI_VERSION_RANGE` against the CLI's own version)
• Publish workflow runs cleanly on merge

[greptile-apps]

Greptile Summary

Version bump to 0.26.0 across all four packages, coordinated to keep CLI_VERSION_RANGE in sync with the CLI's own version while deferring the SDK_VERSION_RANGE update to a follow-up PR (mirroring prior convention).

• cli-node: version → 0.26.0; CLI_VERSION_RANGE → ^0.26.0; SDK_VERSION_RANGE stays at ^0.25.0 intentionally, pending @primitivedotdev/sdk@0.26.0 publish.
• sdk-node, sdk-python, sdk-go: version fields updated to 0.26.0; sdk-python/uv.lock regenerated to match.

Confidence Score: 5/5

Pure version-bump PR with no logic changes; safe to merge.

All six changed files contain only version string updates and the corresponding lock-file regeneration. The intentional asymmetry between CLI_VERSION_RANGE (bumped) and SDK_VERSION_RANGE (held) is explicitly documented in both the PR description and the code comments, matching the established two-PR pattern. No functional code paths were modified.

No files require special attention.

Important Files Changed

Filename	Overview
cli-node/package.json	CLI version bumped from 0.25.2 to 0.26.0
cli-node/src/oclif/commands/functions-init.ts	CLI_VERSION_RANGE bumped to ^0.26.0; SDK_VERSION_RANGE intentionally left at ^0.25.0 pending publish
sdk-go/VERSION	Go SDK version bumped from 0.25.0 to 0.26.0
sdk-node/package.json	Node SDK version bumped from 0.25.2 to 0.26.0
sdk-python/pyproject.toml	Python SDK version bumped from 0.25.0 to 0.26.0
sdk-python/uv.lock	Lock file updated to reflect new 0.26.0 version

_{Reviews (2): Last reviewed commit: "Merge branch 'main' into bump-sdks-0-26-..." | Re-trigger Greptile}