QUIC and HTTP/3 tests should log which exact version of msquic they use

[karelz]

At least to the console -- that will allow us to better check in CI if the right version of msquic is installed (even in future).

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Issue Details

---

At least to the console -- that will allow us to better check in CI if the right version of msquic is installed (even in future).

Author:	karelz
Assignees:	-
Labels:	test-enhancement, area-System.Net.Quic
Milestone:	8.0.0

[CarnaViire]

Tiny note which might be obvious: manually built msquic (from main) will have the same version as the next release will have. So you wouldn't be able to track a switch from manual main to official release package.

Why it might be important: if a release was made to include important changes X, and it has version A.B, making sure that our code uses version A.B is not really enough, because it could be a manual build from main prior to introducing changes X. (this actually happened here #73563 (comment))

[karelz]

Good point. Perhaps we could log more -- incl. date of built msquic.dll, or some other details from it?

[wfurt]

I think when we build msquic our selves or consume mainline, we know what we are up to. I still feel there is value in collecting some basic info.
Perhaps even storing msquic version in static variable so it would be visible in core dumps.