http: call _writeRaw callback when destroyed

[trivikr]

OutgoingMessage._writeRaw() could return early without invoking the write
callback when the message, or its socket, was already destroyed.

This updates _writeRaw() to call the callback with ERR_STREAM_DESTROYED
in those cases, matching the existing destroyed write() behavior.

Fixes: #36673

---

Assisted-by: openai:gpt-5.5

[nodejs-github-bot]

Review requested:

• @nodejs/http
• @nodejs/net

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.07%. Comparing base (0b5b189) to head (ce54af2).
⚠️ Report is 12 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #63447      +/-   ##
==========================================
+ Coverage   90.06%   90.07%   +0.01%     
==========================================
  Files         714      714              
  Lines      225918   225928      +10     
  Branches    42734    42741       +7     
==========================================
+ Hits       203464   203500      +36     
+ Misses      14232    14199      -33     
- Partials     8222     8229       +7     

Files with missing lines	Coverage Δ
lib/_http_outgoing.js	96.16% <100.00%> (+0.36%)	⬆️

... and 31 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/73569/

[pimterry]

Two small comments here, I could easily be persuaded to ignore these if that's complicated for some reason.

One larger issue though: with this PR in place, this code:

'use strict';
const http = require('http');
const { OutgoingMessage } = http;

const server = http.createServer((req, res) => {
  res.on('finish', () => console.log('finish'));
  res.on('error', (e) => console.log(`error:${e.code}`));
  res.on('close', () => {
    console.log('close');
    server.close();
    process.exit(0);
  });

  req.socket.destroy();
  console.log('aborted with destroy()');
  setImmediate(() => {
    // Write after socket destroyed:
    res.end('x');
    console.log('Wrote after socket destroyed');
  });
});

server.listen(0, '127.0.0.1', () => {
  http.get(`http://127.0.0.1:${server.address().port}/`).on('error', () => {});
});

Now prints:

aborted with destroy()
Wrote after socket destroyed
finish
close

I.e. with this change, we now emit 'finish' when ending aborted responses. Without this it skips finish and just closes.

I think that's because the onFinish callback used by end() ignores its error argument and just checks outmsg?.socket?._hadError, which isn't set here.