RFR: 8369920: HttpClient QuicSelectorThread could be a VirtualThread [v4]

[Daniel Fuchs]

> This change makes it possible to use a VirtualThread for the QuicSelectorThread. The default will be to use a VirtualThread on all platforms except the Windows platform. We might consider switching the default for Windows platform too once [JDK-8334574](https://bugs.openjdk.org/browse/JDK-8334574) is fixed.
> 
> The change should be transparent for users of the API. However, using a VirtualThread may result in subtle differences in thread scheduling and class loading, so this change also includes an escape hatch  (a non documented internal system property) that could be used to revert to a platform thread in case of unexpected issues.  That property may be removed in a future version of the JDK.

Daniel Fuchs has updated the pull request incrementally with three additional commits since the last revision:

 - Apply suggestion from @vy
   
   Co-authored-by: Volkan Yazıcı <volkan.yazici at oracle.com>
 - Apply suggestion from @vy
   
   Co-authored-by: Volkan Yazıcı <volkan.yazici at oracle.com>
 - Update the test to match the new property name

-------------

Changes:
  - all: https://git.openjdk.org/jdk/pull/27827/files
  - new: https://git.openjdk.org/jdk/pull/27827/files/3a0b2a69..f5a05218

Webrevs:
 - full: https://webrevs.openjdk.org/?repo=jdk&pr=27827&range=03
 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=27827&range=02-03

  Stats: 13 lines in 1 file changed: 0 ins; 1 del; 12 mod
  Patch: https://git.openjdk.org/jdk/pull/27827.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/27827/head:pull/27827

PR: https://git.openjdk.org/jdk/pull/27827