docs: deploy build path flags, config file auto-detection

Documents --native-build, --depot-build, --local-bundle, --detach and
--build-logs in the deploy command reference, updates the GitHub
integration's config file setting to describe auto-detection, and points
the resource_exhausted troubleshooting entry at the --native-build flag.

Author: myftija

docs/github-integration.mdx

@@ -34,7 +34,7 @@ This eliminates the need to manually run the `trigger.dev deploy` command or set
 <Step title="Customize build settings (optional)">
   Configure how your project is built:
 
-  - **Trigger config file**: Path to your `trigger.config.ts` file. By default, we look for it in the root of your repository. The path should be relative to the root of your repository and contain the config file name, e.g., `apps/tasks/trigger.config.ts`.
+  - **Trigger config file**: Auto-detected by default — we find your `trigger.config.ts` anywhere in your repository. Set a path relative to the root of your repository to override it, e.g., `apps/tasks/trigger.config.ts`. If your repository contains more than one config file, set the path of the one to use.
   - **Install command**: Auto-detected by default, but you can override it if necessary. The command will be run from the root of your repository.
   - **Pre-build command**: Run any commands before building and deploying your project, e.g., `pnpm run prisma:generate`. The command will be run from the root of your repository.
 </Step>

docs/snippets/cli-commands-deploy.mdx

@@ -98,6 +98,30 @@ npx trigger.dev@latest deploy [path]
   briefly before it notices. Requires `--external-id`.
 </ParamField>
 
+<ParamField body="Native build" type="--native-build">
+  Build the image on the Trigger.dev build server. Without a build flag, the server picks the build
+  path for your project.
+</ParamField>
+
+<ParamField body="Depot build" type="--depot-build">
+  Build the image with Depot, ignoring any build path configured on the server.
+</ParamField>
+
+<ParamField body="Local bundle" type="--local-bundle">
+  Install and bundle on your machine, then build the image on the build server from the uploaded
+  bundle. Requires `--native-build`.
+</ParamField>
+
+<ParamField body="Detach" type="--detach">
+  Exit once the build is queued instead of streaming the build logs. The deployment continues on
+  the build server. Requires `--native-build`.
+</ParamField>
+
+<ParamField body="Build logs" type="--build-logs">
+  How build logs are shown: `compact` (default, a single updating line) or `full` (every log line).
+  CI and piped output always use `full`.
+</ParamField>
+
 <ParamField body="Local build" type="--local-build">
   Force building the deployment image locally using your local Docker. This is automatic when self-hosting.
 </ParamField>

docs/troubleshooting.mdx

@@ -87,7 +87,7 @@ Usually there will be some useful guidance below this message. If you can't figu
 
 ### `resource_exhausted`
 
-If you see a `resource_exhausted` error during deploy, the build may have hit resource limits on our build infrastructure. Try our [native builder](https://trigger.dev/changelog/deployments-with-native-builds).
+If you see a `resource_exhausted` error during deploy, the build may have hit resource limits on our build infrastructure. Try our [native builder](https://trigger.dev/changelog/deployments-with-native-builds) by deploying with the `--native-build` flag.
 
 ### `No loader is configured for ".node" files`