Enable crash dumps in AzDo Build pipelines

- [x] This issue is blocking
- [x] This issue is causing unreasonable pain

Recently, we had an intermittent crash in runtime in VMR build for preview 1, but it took multiple days to reproduce the issue and pinpoint what caused the crash. Since there is no infrastructure currently to get crash dumps in AzDO for build pipelines, it was an extremely painful process.

With a complex build such as VMR, it is essential to make diagnosable system and have crash dumps capability in AzDo builds.

It was especially painful to identity the exact VMR commit that introduced the regression. VMR doesn't have a single commit that corresponds to a single commit from the runtime repo. A commit in the VMR represents a batch of commits, one for each repo flowing into installer. So, it was not possible to simply checkout commits in the VMR to identify the specific offending commit in runtime.

cc @markwilkie @agocke @jkotas @mthalman @MichaelSimons @hoyosjs @tommcdon

The issue names AzDo build pipelines and VMR runtime crashes but no files, tests, or entry points. Start by locating the Arcade infrastructure that configures AzDo build pipelines and reviewing how crash diagnostics are collected; done means build failures can provide crash dumps for diagnosing intermittent runtime crashes.

Written by the indexing model from the issue text.