REFUSED_STREAM surfaces as "Write error" instead of being retried #3112

Problem description

This started happening on Node ≥ 24.22.0. Unary calls that are rejected with REFUSED_STREAM now fail with this error instead of being retried automatically:
14 UNAVAILABLE: Write error: Stream closed with error code NGHTTP2_REFUSED_STREAM

This appears to be caused by nodejs/node#66016. When a stream is destroyed, Node now passes the stream error to pending write callbacks. This change in behavior means grpc-js is treating the call as PROCESSED (instead of REFUSED) and skips the automatic retry.

Reproduction steps

I used a grpc-go health server with MaxConnectionAge: 100ms. The client ran 50 concurrent Health/Check calls for 8 seconds using @grpc/grpc-js 1.14.6:
Node v24.21.0: 365,762 successful calls, 0 failures
Node v24.22.1: 386,468 successful calls, 975 REFUSED_STREAM write errors

Additional context

I can put out a PR if you want. Node already sets the rstCode, so we probably just need to carry this info in grpc-js/src/subchannel-call.ts (at least thats what my robot is confirming)