Micro benchmarks don't run anymore

[sebastienros]

Tested in Mvc:

dotnet run -c Release

Output

// Benchmark: NullHtmlEncoderBenchmark.HtmlEncoder: Job-AZLCFO(Runtime=Core, Server=True, Toolchain=.NET Core 3.0, RunStrategy=Throughput)
// *** Execute ***
// Launch: 1 / 1
Did not find f2a5f6e2-9cd2-443e-88ab-37933ea00601.dll in C:\Users\sebros\Documents\Projects\aspnet\AspNetCore\src\mvc\benchmarks\Microsoft.AspNetCore.Mvc.Performance\n\Release\netcoreapp3.0, but the folder contained:
f2a5f6e2-9cd2-443e-88ab-37933ea00601.exe.config
Executable C:\Users\sebros\Documents\Projects\aspnet\AspNetCore\src\mvc\benchmarks\Microsoft.AspNetCore.Mvc.Performance\bin\release\netcoreapp3.0\f2a5f6e2-9cd2-443e-8b-37933ea00601.exe not found
ExitCode != 0
No more Benchmark runs will be launched as NO measurements were obtained from the previous run!

[davidfowl]

Something must have turned off the validation that used to run on build.

[mkArtakMSFT]

Talked to @sebastienros and this seems to be affecting all the repo, rather than just mvc.

[natemcmaster]

Build Team Triage: putting in the backlog. We don't plan to address this right now because we're investing effort in converting this repo to use the Arcade SDK. Benchmark validation runs were a few feature of KoreBuild which does not exist in Arcade. We'll need to design a replacement once we complete #7280

[dougbu]

@sebastienros has anything happened w/ this issue while we weren't looking❔

[dougbu]

@JunTaoLuo please link this into the item @rynowak recently added to the DoI project and remove it from the Build board.

---

Further information: Initial work looks fairly quick based on comments in #13350 e.g.

Arcade does not have support doing a 'dry run' of microbenchmarks projects during the 'Test' phase. See https://github.com/aspnet/BuildTools/blob/803fd176f1ae147aa8af08e49e76ffda7221a4cd/files/KoreBuild/modules/benchmarks/module.targets#L14-L37 for the korebuild implementation

However, it's likely the microbenchmarks themselves haven't been tested lately and are stale. May need to fix a few of them before including them in an AzDO pipeline or running them on Helix.