…ry relaunches

When Node.js apps (e.g. @google/gemini-cli) relaunch themselves via
`spawn(process.execPath, [process.argv[1], ...args])`, the standalone
binary would include the exe path as a user argument in `Deno.args` /
`process.argv`. This is because `process.argv[1]` in standalone mode
is the exe path (set by #32990), and the binary's arg parser only
skipped `argv[0]`.

Now the standalone binary detects when the first CLI arg matches the
current exe path and strips it, preventing the path from leaking into
user arguments.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

…ry relaunches (#33016)

## Summary

Fixes an issue where compiled npm CLI tools that relaunch themselves
(e.g. `@google/gemini-cli`) would have the binary path leak into
`process.argv` as a user argument.

When Node.js apps relaunch themselves they typically do:
```js
spawn(process.execPath, [process.argv[1], ...userArgs])
```

In standalone binaries `process.argv[1]` is the exe path (set by
#32990),
so the child process receives the exe path as its first CLI argument.
The standalone arg parser only skipped `argv[0]`, so the duplicate exe
path ended up in `Deno.args` / `process.argv`, causing yargs-based CLIs
to misinterpret it as a positional argument.

For example, running compiled `gemini` would show the binary path
pre-filled as the initial prompt, because yargs parsed
`/Users/x/.deno/bin/gemini` as a positional arg.

## Fix

In `cli/rt/binary.rs`, detect when the first CLI arg (after skipping
`argv[0]`) matches the current executable path and strip it. This
handles the standard Node.js relaunch pattern without affecting normal
usage.

---------

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>