[release/6.0] [wasm][debugger] Fix (chrome|edge)://inspect for the debug proxy

[github-actions]

Backport of #65216 to release/6.0

The chrome://inspect CDP logic is rejecting /json responses that don't include the content length in the response, this fixes that and allows chrome://inspect to connect to the proxy properly

/cc @lewing

Customer Impact

Without this change the official browser debugger front end is no longer able to connect properly to proxy preventing customers from using chrome or edge as the debugger frontend.

Testing

Manual testing.

Risk

Very low. Simply sets the content-length in the response header

[ghost]

Tagging subscribers to this area: @thaystg
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Backport of #65216 to release/6.0

/cc @lewing

Customer Impact

Testing

Risk

Author:	github-actions[bot]
Assignees:	-
Labels:	area-Debugger-mono
Milestone:	-

[ghost]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Backport of #65216 to release/6.0

The chrome://inspect CDP logic is rejecting /json responses that don't include the content length in the response, this fixes that and allows chrome://inspect to connect to the proxy properly

/cc @lewing

Customer Impact

Without this change the official browser debugger front end is no longer able to connect properly to proxy preventing customers from using chrome or edge as the debugger frontend.

Testing

Manual testing.

Risk

Very low. Simply sets the content-length in the response header

Author:	github-actions[bot]
Assignees:	-
Labels:	Servicing-consider, arch-wasm, area-Debugger-mono
Milestone:	6.0.4

[lewing]

can someone with the appropriate authorization please merge this?

[carlossanlop]

PR has sign-off, the servicing-approved label applied, and the CI is passing. Ready to merge.