fix(cli): TRIGGER_BUILD_SKIP_REWRITE_TIMESTAMP escape hatch

Local self-hosted builds with buildx's docker driver (e.g. orbstack's
default builder) fail on push with:

    exporter option "rewrite-timestamp" conflicts with "unpack"

because the docker driver internally enables `unpack=true` on push,
which is mutually exclusive with `rewrite-timestamp`. Add an opt-out
env var so contributors running `trigger deploy --local-build --push
--builder orbstack` against a local registry can proceed without
switching to a docker-container driver.

Author: ericallam

.changeset/cli-deploy-skip-rewrite-timestamp.md

@@ -0,0 +1,5 @@
+---
+"trigger.dev": patch
+---
+
+Add `TRIGGER_BUILD_SKIP_REWRITE_TIMESTAMP=1` escape hatch for local self-hosted builds whose buildx driver doesn't support `rewrite-timestamp` alongside push (e.g. orbstack's default `docker` driver).

packages/cli-v3/src/deploy/buildImage.ts

@@ -1152,7 +1152,14 @@ function getOutputOptions({
     return outputOptions;
   }
 
-  const outputOptions: string[] = ["type=image", "oci-mediatypes=true", "rewrite-timestamp=true"];
+  // `rewrite-timestamp` is incompatible with the buildx docker driver's
+  // implicit `unpack=true` on push (used by e.g. orbstack's default builder).
+  // Provide an env-var escape hatch so local-dev deploys can opt out.
+  const skipRewriteTimestamp = process.env.TRIGGER_BUILD_SKIP_REWRITE_TIMESTAMP === "1";
+  const outputOptions: string[] = ["type=image", "oci-mediatypes=true"];
+  if (!skipRewriteTimestamp) {
+    outputOptions.push("rewrite-timestamp=true");
+  }
 
   if (imageTag) {
     outputOptions.push(`name=${imageTag}`);