Unable to use `wasm` or `monoaotllvm` as runtime

[caaavik-msft]

With the recent change from #2523, we are unable to use wasm or monoaotllvm in the --runtimes argument like we could previously because the DotNetSdkValidator does not support it. Instead we have to use one which has the .NET version in it such as wasmnet9.0 or monoaotllvmnet9.0. I am not sure what the correct fix for this should be, but the dotnet/performance repo uses these two values for our WASM and Mono AOT LLVM runs, so this is blocking our ability to merge in the latest BDN.

[timcassell]

It looks like those monikers use the current runtime version if Core, or defaults to the earliest available version if Framework.

BenchmarkDotNet/src/BenchmarkDotNet/ConsoleArguments/ConfigParser.cs

Lines 573 to 574 in 9a9d7e7

	case RuntimeMoniker.MonoAOTLLVM:
	return MakeMonoAOTLLVMJob(baseJob, options, RuntimeInformation.IsNetCore ? CoreRuntime.GetCurrentVersion().MsBuildMoniker : "net6.0", runtimeMoniker);

I guess the sdk validator just needs to be updated to use the same logic in GetSdkVersionFromMoniker function.

[LoopedBard3]

Put up a PR that should fix the issue for both wasm and monoaotllvm: #2541