improvement(cli): use batch- for the tables bulk delete, matching its siblings

The CLI renames a bulk form only when it would collide with its singular
sibling, and uses AWS's `batch-` prefix when it does — `files
batch-delete`, `tables rows batch-delete`, `knowledge chunks
batch-update`. `tables delete` exists, so `tables bulk-delete` was that
same rename reaching for the other word, and the only `bulk-` command on
the surface. No `bulk-` CLI command has ever shipped, so this costs
nothing now and would be permanent later.

`files bulk-download` keeps its name: there is no `files download` to
collide with, and it is one archive rather than N operations. Its config
block now says why it exists at all, since the command is never built —
the builder skips non-JSON response modes, but the contract sweeps still
read the entry and require the folder-path field to be marked.

Author: waleedlatif1

apps/docs/content/docs/en/cli/reference.mdx

@@ -3203,12 +3203,12 @@ sim tables groups update <tableId> [options]
 
 </CommandTable>
 
-### sim tables bulk-delete
+### sim tables batch-delete
 
 Bulk Delete Tables and Folders
 
 ```bash
-sim tables bulk-delete [options]
+sim tables batch-delete [options]
 ```
 
 **Options**

apps/docs/content/docs/en/cli/tables.mdx

@@ -201,7 +201,7 @@ sim tables groups update <tableId> [options]
 ## Bulk delete tables and folders
 
 ```bash
-sim tables bulk-delete [options]
+sim tables batch-delete [options]
 ```
 
 **Options**

packages/sim-cli/src/contract/commands.ts

@@ -390,7 +390,9 @@ export const CLI_CONTRACT: CliContract = {
     describe: 'Apply a distinct patch to each listed row',
   },
   bulkDeleteTables: {
-    command: 'tables bulk-delete',
+    // `batch-`, not `bulk-`: `tables delete` exists, so this is the same
+    // collision rename as `files batch-delete` above and takes the same word.
+    command: 'tables batch-delete',
     flags: { folderPaths: FOLDER_PATHS_FLAG },
     confirm: 'This deletes every listed table and all of their rows.',
   },
@@ -842,6 +844,13 @@ export const CLI_CONTRACT: CliContract = {
     describe: 'Unzip an archive into a new folder beside it',
     confirm: 'This writes every file in the archive into the workspace.',
   },
+  /**
+   * Configured even though `buildGeneratedCommands` skips it: it only builds
+   * operations whose `responseMode` is `json` (runtime/build.ts), so this
+   * zip-streaming endpoint has no command today. The entry is not inert — the
+   * contract sweeps read it, and `folderPaths` must be marked for encoding
+   * here or `folder-path fields` fails.
+   */
   bulkDownloadFiles: {
     command: 'files bulk-download',
     describe: 'Download files and folders as a zip archive',