Un-pin @connectrpc/connect-node to v2 once TS SDK lands it

[jeremyrose-viam]

#5251 pinned @connectrpc/connect-node to v1 in docs/build-apps/setup/node.md because an unpinned install grabs the incompatible Connect-ES v2 line and crashes (found while fixing the TS-sample CI failures in #5119).

The real fix is upstream: the TS SDK needs to move to the v2 line itself. That's tracked in viamrobotics/viam-typescript-sdk#987 ("Bump undici and @connectrpc/connect-node"), currently open.

Docs' own copy of this same Dependabot bump (#5254) was closed for the same reason and will likely recur — close/ignore it until viamrobotics/viam-typescript-sdk#987 merges.

When viamrobotics/viam-typescript-sdk#987 merges:

• Remove the v1 pin note added in Pin @connectrpc/connect-node to v1 in Node.js setup docs #5251 from docs/build-apps/setup/node.md
• Bump @connectrpc/connect-node in root package.json (currently pinned ^1.7.0) — separate from the doc pin above
• Re-check connectNode.createGrpcTransport({ httpVersion: "2", ...opts }) against the v2 API in the 4 example files that import @connectrpc/connect-node directly (touched by Replace @koush/wrtc with node-datachannel in TS code samples #5250):
  • static/include/examples/vision/test-vision-methods.ts
  • static/include/examples/metadata/add-metadata.ts
  • static/include/examples/run-inference/run-vision-service.ts
  • static/include/examples/capture-annotate-images/label-images.ts
• Re-run the TS example CI (issue CI failure: Test Code Samples #5119) to confirm no regressions
• Close this issue