Add default method support to virtual statics

[davidwrighton]

• The preview feature version of virtual statics implemented for .NET 6 does not allow for the interface methods to have a default implementation.
• With this change, we add support for the interface method having an actual implementation to CoreCLR. From what I can tell the Mono runtime already had such support
• There are some small ECMA spec updates to allow this change that are also included

In addition, I've taken the liberty to enable running the coreclr test suite on Mono on Windows. It needed a small amount of fixup.

[davidwrighton]

@vargaz When I run the new tests on Mono, they fail with crashes after 12 tests. However, we ALSO fail with a crash after 12 tests in the old test which hasn't been changed. When do we plan to fix this test suite for Mono?
@MichalStrehovsky I have not updated anything in NativeAOT. Have static virtuals been implemented for NativeAOT yet or are you waiting for the Crossgen2 implementation to be implemented?
@trylek fyi

[MichalStrehovsky]

@MichalStrehovsky I have not updated anything in NativeAOT. Have static virtuals been implemented for NativeAOT yet or are you waiting for the Crossgen2 implementation to be implemented?

I've been waiting for the type system change part of #54063 but since it looks like it might not land anytime soon, I might just take the type system part, finish it, and run with it. Might not get to that soon either though. But it looks like NativeAOT has more urgency for that for .NET 7 than crossgen2 has.

[trylek]

This is indeed very nice and clean, thanks David! The expanded test set will be of immense help when stabilizing SVM resolution in Crossgen2 in the presence of default interface methods.

[davidwrighton]

/azp list

[azure-pipelines]

CI/CD Pipelines for this repository:

• coreclr-gc-longrunning
• coreclr-gc-simulator
• runtime-coreclr outerloop
• runtime-coreclr jitstress
• runtime-coreclr jitstressregs
• runtime-coreclr jitstress2-jitstressregs
• runtime-coreclr gcstress0x3-gcstress0xc
• runtime-coreclr gcstress-extra
• runtime-coreclr r2r-extra
• runtime-coreclr jitstress-isas-x86
• runtime-coreclr jitstress-isas-arm
• runtime-coreclr jitstressregs-x86
• runtime-coreclr libraries-jitstressregs
• runtime-coreclr libraries-jitstress2-jitstressregs
• runtime-coreclr r2r
• runtime-coreclr runincontext
• runtime-coreclr crossgen2
• runtime-libraries-coreclr outerloop
• runtime-libraries-coreclr outerloop-windows
• runtime-libraries-coreclr outerloop-linux
• runtime-libraries-coreclr outerloop-osx
• runtime
• runtime-libraries enterprise-linux
• runtime-libraries stress-http
• runtime-libraries stress-ssl
• runtime-dev-innerloop
• runtime-coreclr crossgen2 outerloop
• coreclr-release-outerloop-nightly
• sync-runtime-to-mono
• runtime-coreclr crossgen2-composite
• runtime-jit-experimental
• runtime-coreclr libraries-jitstress
• dotnet-linker-tests
• runtime-coreclr ilasm
• runtime-coreclr crossgen2-composite gcstress
• runtime-libraries-mono outerloop
• runtime-staging
• runtime-coreclr pgo
• runtime-coreclr libraries-pgo
• coreclr-gc-regions
• Antigen
• runtime-community
• Fuzzlyn
• runtime-coreclr superpmi-replay
• wasm-debugger
• runtime-coreclr superpmi-asmdiffs
• runtime-coreclr superpmi-asmdiffs-checked-release
• runtime-manual
• runtime-extra-platforms
• jit-cfg

[davidwrighton]

/azp run runtime-coreclr crossgen2 outerloop

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[davidwrighton]

Running an outerloop crossgen test to make sure that the rather long new test names don't cause significant issues in our test suite.

[davidwrighton]

/azp run runtime-coreclr crossgen2 outerloop

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[marek-safar]

/cc @SamMonoRT