fix(opencode): patch gcp metadata warning leak (#29431)

Author: rekram1-node

bun.lock

@@ -144,6 +144,7 @@
     "@standard-community/standard-openapi@0.2.9": "patches/@standard-community%2Fstandard-openapi@0.2.9.patch",
     "solid-js@1.9.10": "patches/solid-js@1.9.10.patch",
     "virtua@0.49.1": "patches/virtua@0.49.1.patch",
-    "@ai-sdk/xai@3.0.82": "patches/@ai-sdk%2Fxai@3.0.82.patch"
+    "@ai-sdk/xai@3.0.82": "patches/@ai-sdk%2Fxai@3.0.82.patch",
+    "gcp-metadata@8.1.2": "patches/gcp-metadata@8.1.2.patch"
   }
 }

package.json

@@ -0,0 +1,14 @@
+diff --git a/build/src/index.js b/build/src/index.js
+--- a/build/src/index.js
++++ b/build/src/index.js
+@@ -323,6 +323,10 @@ async function isAvailable() {
+         if (process.env.DEBUG_AUTH) {
+             console.info(err);
+         }
++        // Promise.any() rejects with AggregateError when neither metadata host
++        // is available. This is expected outside GCP, not a warning condition.
++        if (err instanceof AggregateError)
++            return false;
+         if (err.type === 'request-timeout') {
+             // If running in a GCP environment, metadata endpoint should return
+             // within ms.