Extension Development Host Debug Console shows DEP0040/DEP0169 from extensionHostProcess.js

### VS Code version

1.131.0 (e4c7e7b1d6d060162f4aa7f8225271b67ce1df75) x64 — Windows

### Steps to reproduce

1. Open any VS Code extension project with an `extensionHost` launch config (example: https://github.com/biomejs/biome-vscode).
2. Start debugging with **F5** (`type: "extensionHost"`).
3. Look at the **parent** window Debug Console (not the Extension Development Host).

### Expected

Debug Console stays quiet unless the extension under test logs something actionable.

### Actual

Red `DeprecationWarning` noise attributed to VS Code's own extension host:

```text
(node:…) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `Code --trace-deprecation ...` to show where the warning was created) …extensionHostProcess.js:679
(node:…) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. …
```

Stack/source shown in the Debug Console points at `extensionHostProcess.js` (VS Code), not extension source. Reproduced with `--disable-extensions` so only the extension under development is loaded.

This is easy to misread as an extension failure while debugging. Related CLI-side report: #326998 (DEP0169 on `code --install-extension`).

### Request

Please migrate remaining `punycode` / `url.parse()` usage in the extension host (or suppress these known Node deprecations in the Extension Development Host debug session until that lands), so F5 Debug Console doesn't light up red for VS Code-internal debt.