[🚀 Feature]: [dotnet] Upgrade `System.Text.Json` to v9?

[nvborisenko]

Description

Currently we use v8, with issue: dotnet/runtime#72604

We applied a workaround to avoid this issue. For Selenium team it is not a big deal to support this workaround.

Have you considered any alternatives or workarounds?

What if we upgrade to System.Text.Json v9, meaning this workaround is no longer needed.

But if we upgrade, then we should get some benefits.

I can image the following benefits:

• Support polymorphic deserialization with unordered discriminator
• Introduce deserialization from Stream. Currently we are listening incoming WebSocket chunks, and start deserialization process as soon as all message's chunks are received. If v9 can help us to start deserialization process as soon as any chunk is available (from Stream), then it can be beneficial. We should test it on large json payloads and see memory consumption. If memory usage decreases significantly, then it is good argument to upgrade.

[selenium-ci]

@nvborisenko, thank you for creating this issue. We will troubleshoot it as soon as we can.

Selenium Triage Team: remember to follow the Triage Guide

[nvborisenko]

The streaming deserialization is also available in v8, via JsonDocument.ParseAsync(stream). So it is not argument to upgrade the package.

[nvborisenko]

Not yet, it is still not big deal to use as minimum as possible.. it is still possible.