fix(bundle): avoid esbuild protocol deadlock (#36427)
## Summary
- update `esbuild_client` from 0.7.1 to 0.7.2
- include the protocol deadlock fix from denoland/esbuild_client#18
## Root cause
The esbuild protocol reader and writer share one select loop and
communicate through bounded channels. Under load, packet forwarding
could wait for the packet handler while the handler waited inline for
response-channel capacity, leaving each side dependent on the other.
`esbuild_client` 0.7.2 moves `ping` and `on-start` response delivery out
of the packet-dispatch path, breaking that circular wait while
preserving bounded queues.
Fixes #36417.
## Validation
- `./tools/format.js --check Cargo.lock cli/Cargo.toml`
- `cargo build -p deno --bin deno`
- `./x test-spec 'specs::bundle::'` (65 tests)