fix(ext/fetch): update h2 to fix sending a PROTOCOL_ERROR instead of REFUSED_STREAM when receiving oversized headers

[Cre3per]

Fixes #26490

Related PR in h2 hyperium/h2#792
Related release of h2 https://github.com/hyperium/h2/releases/tag/v0.4.6

No test case, as the changes don't affect deno's code directly and I haven't fully grasped why the promise never resolved. The following script can be used to test manually

// blocks with h2<0.4.6. fails with h2>=0.4.6.
await fetch("https://finance.yahoo.com/currencies/", {
      headers: {
        "User-Agent":
          "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.0.0 Safari/537.36",
      },
    });

new output

error: Uncaught (in promise) TypeError: error sending request from -snip- for https://finance.yahoo.com/markets/currencies/ (188.125.94.206:443): client error (SendRequest): http2 error: stream error detected: unspecific protocol error detected
     await fetch("https://finance.yahoo.com/markets/currencies/", {
     ^
    at mainFetch (ext:deno_fetch/26_fetch.js:202:11)
    at eventLoopTick (ext:core/01_core.js:175:7)
    at async fetch (ext:deno_fetch/26_fetch.js:454:11)
    at async request.ts:1:6
Caused by: Error: stream error detected: unspecific protocol error detected
    at mainFetch (ext:deno_fetch/26_fetch.js:202:43)
    at eventLoopTick (ext:core/01_core.js:175:7)
    at async fetch (ext:deno_fetch/26_fetch.js:454:11)
    at async request.ts:1:6

This error message is not very helpful, see #26490 for node's output, which explains what went wrong.

• Do we want to open a new issue to try to improve the error message? (Reported error is hyper_util::client::legacy::Error(SendRequest, hyper::Error(Http2, Error { kind: Reset(StreamId(1), PROTOCOL_ERROR, Library) })), might be non-trivial)
• Does deno have a flag akin to node's --max-http-header-size which would allow the request to finish successfully? Related Max Header Size #21047 @littledivy

[CLAassistant]

All committers have signed the CLA.

[Cre3per]

force-pushed to correct mail address

[Cre3per]

check failure looks like a filesystem timing issue unrelated to this PR. I couldn't find other pipelines with this failure though.