DOC-429: Move Global options table to the Overview page

Mirrors the same fix agreed on the AWS docs sync PR (#912): Global
options apply to everyday interactive use, not just automation/CI,
so move the table from automation.mdx to index.mdx, right after
Quick start, keeping the detailed sections (Structured output) on
automation.mdx with an absolute-path cross-reference.

Author: quetzalliwrites

src/content/docs/azure/developer-tools/lstk/automation.mdx

@@ -1,27 +1,10 @@
 ---
 title: lstk Automation & CI
-description: Global options, non-interactive mode, structured JSON output, environment variables, tracing, and logging for scripting lstk.
+description: Non-interactive mode, structured JSON output, environment variables, tracing, and logging for scripting lstk.
 template: doc
 tags: ['Hobby']
 ---
 
-## Global options
-
-These options are available for all commands:
-
-| Option              | Description                                                                |
-|:--------------------|:------------------------------------------------------------------------------|
-| `--config <path>`   | Path to a specific TOML config file                                        |
-| `--non-interactive` | Disable the interactive TUI, use plain output                              |
-| `--json`            | Emit a single machine-readable JSON envelope on stdout instead of human-oriented output. Supported by `stop`, `reset`, and `update`; any other command rejects it. See [Structured output](#structured-output). |
-| `--persist`         | Persist emulator state across restarts (on `start`/bare `lstk` and `restart`) |
-| `--type <type>`, `-t <type>` | Emulator type to start: `aws`, `snowflake`, or `azure` (on `start`/bare `lstk`; records the choice in config). See [Selecting the emulator with `--type`](/azure/developer-tools/lstk/lifecycle-commands/#selecting-the-emulator-with---type). |
-| `--snapshot <REF>`  | Snapshot REF to auto-load after start (on `start`/bare `lstk`; overrides config for one run) |
-| `--no-snapshot`     | Skip auto-loading the configured snapshot (on `start`/bare `lstk`)          |
-| `--timeout <duration>` | Startup readiness deadline for `start`/bare `lstk`, as a Go duration; overrides `LSTK_STARTUP_TIMEOUT` for one run. See [`start`](/azure/developer-tools/lstk/lifecycle-commands/#start). |
-| `-v`, `--version`   | Print the version and exit                                                 |
-| `-h`, `--help`      | Print help and exit                                                        |
-
 ## Interactive and non-interactive mode
 
 `lstk` automatically selects its output mode:

src/content/docs/azure/developer-tools/lstk/index.mdx

@@ -20,13 +20,13 @@ Running `lstk` with no arguments takes you through the entire startup flow autom
 
 This section is split into focused pages:
 
-- **Overview** (this page): installation, quick start, and shell completions.
+- **Overview** (this page): installation, quick start, global options, and shell completions.
 - [Authentication](/azure/developer-tools/lstk/authentication/): logging in and out, and how `lstk` resolves your auth token.
 - [Configuration](/azure/developer-tools/lstk/configuration/): the `config.toml` file, emulator types, environment variables, and volumes.
 - [Lifecycle commands](/azure/developer-tools/lstk/lifecycle-commands/): `start`, `stop`, `restart`, `status`, `logs`, `reset`, `volume`.
 - [Cloud & IaC commands](/azure/developer-tools/lstk/cloud-and-iac-commands/): `aws`, `az`, `terraform`, `cdk`, `sam`.
 - [Snapshots](/azure/developer-tools/lstk/snapshots/): save and load emulator state with `snapshot save`/`load`/`list`/`remove`/`show`.
-- [Automation & CI](/azure/developer-tools/lstk/automation/): global options, non-interactive mode, structured output, and environment variables.
+- [Automation & CI](/azure/developer-tools/lstk/automation/): non-interactive mode, structured output, and environment variables.
 - [Setup & maintenance](/azure/developer-tools/lstk/setup-and-maintenance/): `setup`, `config`, `update`, and offline/enterprise environments.
 - [FAQ & Troubleshooting](/azure/developer-tools/lstk/faq-and-troubleshooting/).
 
@@ -102,6 +102,25 @@ LOCALSTACK_AUTH_TOKEN=<your-ci-auth-token> lstk --non-interactive
 
 CI environments require a CI Auth Token; a personal Developer Auth Token cannot be used there.
 
+## Global options
+
+These options are available for all commands:
+
+| Option              | Description                                                                |
+|:--------------------|:------------------------------------------------------------------------------|
+| `--config <path>`   | Path to a specific TOML config file                                        |
+| `--non-interactive` | Disable the interactive TUI, use plain output                              |
+| `--json`            | Emit a single machine-readable JSON envelope on stdout instead of human-oriented output. Supported by `stop`, `reset`, and `update`; any other command rejects it. See [Structured output](/azure/developer-tools/lstk/automation/#structured-output). |
+| `--persist`         | Persist emulator state across restarts (on `start`/bare `lstk` and `restart`) |
+| `--type <type>`, `-t <type>` | Emulator type to start: `aws`, `snowflake`, or `azure` (on `start`/bare `lstk`; records the choice in config). See [Selecting the emulator with `--type`](/azure/developer-tools/lstk/lifecycle-commands/#selecting-the-emulator-with---type). |
+| `--snapshot <REF>`  | Snapshot REF to auto-load after start (on `start`/bare `lstk`; overrides config for one run) |
+| `--no-snapshot`     | Skip auto-loading the configured snapshot (on `start`/bare `lstk`)          |
+| `--timeout <duration>` | Startup readiness deadline for `start`/bare `lstk`, as a Go duration; overrides `LSTK_STARTUP_TIMEOUT` for one run. See [`start`](/azure/developer-tools/lstk/lifecycle-commands/#start). |
+| `-v`, `--version`   | Print the version and exit                                                 |
+| `-h`, `--help`      | Print help and exit                                                        |
+
+These apply to both interactive and non-interactive (scripted/CI) use, see [Automation & CI](/azure/developer-tools/lstk/automation/) for the details behind `--non-interactive` and `--json`.
+
 ## Shell completions
 
 `lstk` includes completion scripts for bash, zsh, fish, and powershell.