fix: pass full response headers in net module

[zcbenz]

Description of Change

Close #20631.

Use raw headers instead of filtered headers in net module. This is a regression caused by network service refactoring.

Checklist

• PR description included and stakeholders cc'd
• npm test passes
• tests are changed or added
• PR title follows semantic commit guidelines
• PR release notes describe the change in a way relevant to app developers, and are capitalized, punctuated, and past tense.

Release Notes

Notes: Fix set-cookie header not passed in net module.

[nornagon]

What other kinds of filtering is Chromium doing here? Is it doing any sort of normalization that we might not want to lose? Do we only need the set-cookie headers here?

[zcbenz]

What other kinds of filtering is Chromium doing here? Is it doing any sort of normalization that we might not want to lose? Do we only need the set-cookie headers here?

The raw headers are populated from net::URLRequest::response_headers(), and it is the same with 6.x, which uses net::URLRequest directly:
https://cs.chromium.org/chromium/src/services/network/loader_util.cc?type=cs&sq=package:chromium&g=0&l=102-120

Currently I'm only aware the set-cookie has been filtered because Chromium blocks third party cookies. I couldn't find a way to work around this without patching Chromium as the requests of net module are sent from browser process, and setting cookie sites does not seem to work.

[zcbenz]

@nornagon Can you take another look at this?

[release-clerk]

Release Notes Persisted

Fix set-cookie header not passed in net module.

[trop]

I have automatically backported this PR to "8-x-y", please check out #21769

[trop]

I have automatically backported this PR to "7-1-x", please check out #21770