Enable AddressSanitizer on Debug and Checked builds for both MSVC and Clang

[jkoritzinsky]

AddressSanitizer is a tool that helps with common bugs like use-out-of-scope, buffer-overflow, use-after-free, etc. It is supported on GCC, Clang, and newer versions of MSVC.

Today, we use Run-Time Checks on MSVC to validate some of these scenarios, but we don't run any equivalent on non-MSVC builds. We have some infrastructure for running AddressSanitizer on Clang builds, but we've never enabled it for our builds (some partners have enabled it for theirs at various times).

By enabling AddressSanitizer for both our MSVC and Clang builds, we would ensure that we validate our code against common classes of bugs in C and C++.

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

Issue Details

---

AddressSanitizer is a tool that helps with common bugs like use-out-of-scope, buffer-overflow, use-after-free, etc. It is supported on GCC, Clang, and newer versions of MSVC.

Today, we use Run-Time Checks on MSVC to validate some of these scenarios, but we don't run any equivalent on non-MSVC builds. We have some infrastructure for running AddressSanitizer on Clang builds, but we've never enabled it for our builds (some partners have enabled it for theirs at various times).

By enabling AddressSanitizer for both our MSVC and Clang builds, we would ensure that we validate our code against common classes of bugs in C and C++.

Author:	jkoritzinsky
Assignees:	-
Labels:	area-Infrastructure, tenet-reliability
Milestone:	-

[jkoritzinsky]

We've enabled ASAN though a new command line option instead of per-config.