Blazor WebAssembly & WebView JS to .NET Streaming Interop Support

[TanayParikh]

• Adds support for Blazor WebAssembly & WebView JS to .NET Streaming Interop
• Refactored the logic from RemoteJSDataStream into a shared BaseJSDataStream which is shared across the 3 platforms. Did this instead of putting it into JSInterop to avoid creating additional public APIs per Javier's recommendation.
• TODO:
  • WASM/WebView unhandled exceptions.
  • WebView interop mechanism for ReceiveJSDataChunk needs to be refined (potential synchronization issue)
  • Update WASM Baselines to fix CI: https://github.com/dotnet/aspnetcore/tree/main/src/Components/WebAssembly/testassets/WasmLinkerTest
  • WASM try different chunk sizes (will do this after everything else is approved)
  • Tests still need to be refactored a bit to reflect BaseJSDataStream (will do this after everything else is approved)

Fixes: #33638
Fixes: #27862
Part of: #30289

[SteveSandersonMS]

Awesome work @TanayParikh! This looks great to me.

[TanayParikh]

fyi/ Had to change the WebView base64 serialization slightly due to stack overflow concerns on large byte arrays.

[TanayParikh]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[TanayParikh]

CI passed but status isn't being reported for some reason. Could someone with admin rights please merge? @dotnet/aspnet-build

https://dev.azure.com/dnceng/public/_build/results?buildId=1239168&view=results

[dougbu]

@TanayParikh all closing and reopening did was cancel the auto-merge and start another build that likely won't report back to GitHub either 😀

[TanayParikh]

@TanayParikh all closing and reopening did was cancel the auto-merge and start another build that likely won't report back to GitHub either 😀

Thanks for merging. Wasn't sure why the CI status wasn't being reported to GitHub and figured closing/re-opening may re-trigger the reporting (of the new CI run).