fix(vtex): bump @decocms/runtime to ^1.6.2 to restore state propagation (#430)

The kubernetes-bun rollback in #429 dropped @decocms/runtime from ^1.6.2
back to 1.3.1. With 1.3.1, requests reach the pod with a populated
MESH_REQUEST_CONTEXT envelope (token/connectionId/meshUrl all set) but
state arrives as an empty object — so state.accountName is null and
every tool call fails with "VTEX accountName is missing".

Confirmed in the deployed pod logs:
  hasMeshContext: true, hasToken: true, hasConnectionId: true,
  hasMeshUrl: true, stateKeys: [], stateAccountNamePresent: false

The Workers latency that prompted the revert was startup-CPU-budget
specific to Cloudflare Workers, not a Bun problem, so this only bumps
the runtime/bindings/sdk versions and keeps the kubernetes-bun deploy
and serve()-style entrypoint intact.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: viktormarinho

bun.lock

@@ -18,16 +18,16 @@
     "test": "bun test"
   },
   "dependencies": {
-    "@decocms/bindings": "^1.3.1",
-    "@decocms/runtime": "1.3.1",
+    "@decocms/bindings": "^1.4.0",
+    "@decocms/runtime": "^1.6.2",
+    "@modelcontextprotocol/sdk": "^1.27.1",
     "zod": "^4.0.0"
   },
   "devDependencies": {
     "@cloudflare/workers-types": "^4.20260206.0",
     "@decocms/mcps-shared": "1.0.0",
     "@hey-api/client-fetch": "^0.8.0",
     "@hey-api/openapi-ts": "0.92.4",
-    "@modelcontextprotocol/sdk": "1.20.2",
     "@types/bun": "^1.2.14",
     "deco-cli": "^0.28.0",
     "typescript": "^5.7.2"