#21000: fix: resolve option collision between browser and cookies set commands

Fixes #20976 ## What changed - Renamed the global/parent '--url' option to '--gateway-url' in the gateway client options to avoid collision with the '--url' required option in the 'browser cookies set' subcommand. - Updated GatewayRpcOpts type to use 'gatewayUrl' instead of 'url' - Updated all usages in callGatewayFromCli and logs-cli.ts ## AI-assisted contribution - This fix was generated by an AI agent (OpenClaw cron: gh-issues-fix) - Testing depth: validated with pnpm build && pnpm check && pnpm test - The fix addresses the root cause described in the issue by renaming the parent command's --url option to avoid collision with the cookies set subcommand's required --url option <!-- greptile_comment --> <h3>Greptile Summary</h3> Renamed the global `--url` option to `--gateway-url` in gateway client options to prevent collision with the `--url` required option in the `browser cookies set` subcommand. Updated `GatewayRpcOpts` type and all usages in `callGatewayFromCli` and `logs-cli.ts`. The fix correctly resolves the option collision issue described in #20976. <h3>Confidence Score: 5/5</h3> - This PR is safe to merge with minimal risk - The changes are straightforward and focused: renaming a single CLI option to avoid collision. All usages have been correctly updated in both type definitions and implementations. The fix directly addresses the reported issue and follows a clear renaming pattern. No logic changes, no security implications. - No files require special attention _{Last reviewed commit: 117ccfc} <!-- greptile_other_comments_section --> <!-- /greptile_comment -->