Thrown error in writeHead when statusMessage exists in http2

[bjohansebas]

When http2 was written in Node.js, from what I've read, it was intended to have a high degree of compatibility with http1, bringing with it warnings such as when using writeHead with statusMessage. I know that at this time having statusMessage is ignored, but maybe it's time to move forward and throw an error instead of just a warning.

Part of this was the expected behavior while explicitly supporting http2 in on-headers in jshttp/on-headers#16.
I understand that this is also a breaking change, so it could be a candidate for Node 25/26.

WDYT?

[bjohansebas]

Well, it's actually not necessary to throw an exception, just to disallow it and assume that writeHead will only take two arguments.