Fix: require a value on the ADK CLI options that always take one

[AmaadMartin]

Please ensure you have read the contribution guide before creating a pull request.

Link to Issue or Description of Change

1. Link to an existing issue (if applicable):
   No issue. This came out of a CLI audit.
2. Or, if no issue exists, describe the change:
   Problem: Commander treats [value] as an optional argument, so adk deploy cloud_run --project stores the boolean true instead of a string. The action handler types its options as Record<string, string>, so TypeScript does not catch the boolean. deployToCloudRun then skips the gcloud-config fallback and writes ENV GOOGLE_CLOUD_PROJECT=true into the generated Dockerfile. Twelve options have this shape, and none of them has a meaningful "present but valueless" state.

Solution: I declared those twelve options with <value>, so commander rejects the command before the action handler runs. The long names, placeholder words, help text and defaults are unchanged, and every form that supplies a value behaves exactly as before, including --project=. The boolean flags keep [boolean]; #693 handles those, and a new test pins --with_ui so this change cannot leak into them. Commander owns the error, so there is no validation branch and no argParser.

Two limits stay as they are. --project ./agents still swallows the directory, and --project --region us-west1 now yields project === '--region' instead of project === true. Commander consumes the next token either way.

Collision check: I listed the 300 open PRs on the fork and read the diffs of the nine that touch dev/src/cli/cli.ts (#585, #587, #592, #693, #694, #695, #700, #705, #706). None changes a [string], [id] or [dir] option. #693 is the closest neighbour and is disjoint: it converts the [boolean] flags. I branched from main because no open PR is a prerequisite.

Testing Plan

Please describe the tests that you ran to verify your changes. This is required for all PRs that are not small documentation or typo fixes.
Unit Tests:
[x] I have added or updated unit tests for my change.
[x] All unit tests pass locally.

npx vitest run --project unit:dev dev/test/cli/cli_test.ts -> 44 passed (25 existing, 19 new). No existing test was changed or removed.

The existing harness calls program.exitOverride() after createProgram() has built the subcommands. Commander copies the exit callback at .command() time, so the override never reaches deploy cloud_run, and a missing-argument error would call process.exit and kill the vitest worker. A new applyExitOverrideRecursively helper, applied in a nested beforeEach, fixes that without touching the existing setup.

Proof each new test can fail. I mutated dev/src/cli/cli.ts and reran the file:

Mutation	Result
'--project <string>' -> '--project [string]'	2 failed. promise resolved "undefined" instead of rejecting
all twelve reverted to [...]	13 failed, one per rejection case
'--with_ui [boolean]' -> '<boolean>' (over-application)	3 failed, including should still accept --with_ui as the last token: error: option '--with_ui <boolean>' argument missing
'--project <string>' -> '<string...>'	6 failed, including the positional and empty-value cases: expected { …(16) } to match object { project: 'p', …(1) }
'--agent_engine_id <id>' -> '<id...>'	4 failed, including the agent-engine positional case
'--tests_dir <dir>' -> '--tests_dir'	2 failed: error: too many arguments for 'conformance'

Coverage: the change adds no line and no branch to dev/src/cli.

Manual End-to-End (E2E) Tests:
Please provide instructions on how to manually test your changes, including any necessary setup or configuration.

Run npm run build, then:

1. node dev/dist/esm/cli_entrypoint.js deploy cloud_run --project prints error: option '--project <string>' argument missing and exits 1. I confirmed no temp directory and no Dockerfile were created.
2. node dev/dist/esm/cli_entrypoint.js integration conformance --agents_dir prints error: option '--agents_dir <dir>' argument missing and exits 1.
3. node dev/dist/esm/cli_entrypoint.js deploy cloud_run --help lists every option with unchanged help text. The twelve now show <...>; --with_ui, --verbose, --compile, --bundle and --a2a still show [boolean].

CI: run-tests passes on ubuntu, macOS and windows. The first windows run failed on two timeouts in tests/integration/app_loader/app_loader_test.ts, a file this PR does not touch and which does not use the CLI parser. The job passed on re-run with no code change, so the timeout is a flake; #545 targets it.

I also validated locally on the pushed commit:

• npx vitest run --project unit:dev dev/test/cli/cli_test.ts -> 44 passed.
• npm run build -> succeeds.
• npx eslint dev/src/cli/cli.ts dev/test/cli/cli_test.ts -> clean.
• npx prettier --check dev/src/cli/cli.ts dev/test/cli/cli_test.ts -> clean.
• npm run ts:check reports the same 42 pre-existing failing files before and after this change. None of them is in dev/src/cli or dev/test/cli.

Checklist

[x] I have read the CONTRIBUTING.md document.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have added tests that prove my fix is effective or that my feature works.
[x] New and existing unit tests pass locally with my changes.