[browser] enable HttpStreamingDisabledBy_WasmEnableStreamingResponse_InProject test

[pavelsavara]

Depends on dotnet/sdk#50000
Fixes #113628

[dotnet-policy-service]

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

[pavelsavara]

/azp run runtime-wasm

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[pavelsavara]

@akoeplinger please could you merge main when the re-bootstreap happens and merge this if the build is green. I'm out of office till Mon.

Thank you!

[Copilot]

Pull Request Overview

This PR enables a previously disabled test (HttpStreamingDisabledBy_WasmEnableStreamingResponse_InProject) by removing the ActiveIssue attribute and removing the runtime configuration option that was setting System.Net.Http.WasmEnableStreamingResponse in the browser build targets.

Key changes:

• Removes the runtime configuration option for System.Net.Http.WasmEnableStreamingResponse from browser build targets
• Re-enables a test that was previously disabled due to issue #113628

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
src/mono/browser/build/BrowserWasmApp.targets	Removes the RuntimeHostConfigurationOption for System.Net.Http.WasmEnableStreamingResponse
src/libraries/System.Runtime.InteropServices.JavaScript/tests/.../HttpRequestMessageTest.cs	Removes ActiveIssue attribute to re-enable the HttpStreamingDisabledBy_WasmEnableStreamingResponse_InProject test

---

_{You can also share your feedback on Copilot code review for a chance to win a $100 gift card. Take the survey.}

[akoeplinger]

/ba-g test failures are unrelated issues