The following needs to be done

• Bump main to 9.0 in eng/Versions.props --> in PR #157
• Update Maestro default channel configuration for main to the .NET 9 channel
• Update the subscriptions to flow msquic .NET 9 into runtime main.

I also noticed that https://github.com/dotnet/msquic/blob/main/FLOW.md is outdated since there are more branches and different msquic versions now. --> in PR #157

Contributes to dotnet/runtime#92502

/cc @dotnet/ncl

After a recent update of lttng-ust from 2.12 to 2.13 it's not possible to build msquic with logging on.
Build error (whole build.log attached):

[ 79%] Building CXX object src/tools/attack/CMakeFiles/quicattack.dir/attack.cpp.o
In file included from /usr/include/lttng/ust-utils.h:16,
                 from /usr/include/lttng/ust-tracer.h:14,
                 from /usr/include/lttng/tracepoint.h:21,
                 from /home/manicka/repositories/msquic/src/generated/linux/operation.h.clog.h:10,
                 from /home/manicka/repositories/msquic/src/core/operation.h:9,
                 from /home/manicka/repositories/msquic/src/core/precomp.h:55,
                 from /home/manicka/repositories/msquic/src/tools/attack/attack.cpp:14:
/usr/include/c++/11.1.0/type_traits:56:3: error: template with C linkage
   56 |   template<typename _Tp, _Tp __v>
      |   ^~~~~~~~
In file included from /home/manicka/repositories/msquic/src/tools/attack/attack.cpp:14:
/home/manicka/repositories/msquic/src/core/precomp.h:40:1: note: ‘extern "C"’ linkage started here
   40 | extern "C" {
      | ^~~~~~~~~~

Also sharing the lttng header files lttng-headers.tar.gz

I'm not blocked by this, I can downgrade and keep the older version. I just thought this might be something that would need to be solved in the future anyway.

cc: @wfurt

msquic statically links the CRT on Windows. This is different from how CoreCLR (and other CoreCLR components) link the CRT - they link to UCRT dynamically.

This has three effects:

• msquic.dll is likely a lot bigger than it needs to (we saw 200 kB savings when NativeAOT switched to UCRT a couple weeks back: dotnet/runtime#71182).
• Bigger size means bigger working set impact.
• Security fixes done to the CRT will not be automatically picked up when the OS is serviced

Cc @vitek-karas @sbomer @karelz @wfurt

Should this repo have a subscription so that dotnet/runtime's release/6.0 branch gets updates from msquic release/6.0?

@dotnet/ncl @mmitche