Add address sanitizer flags

[englercj]

What does this PR do?

Resolves #1595

1. Implement support for fsanitize=address in gcc, clang, msc, and Visual Studio backends.
2. Implement support for fsanitize=fuzzer in msc, Visual Studio, and clang backends.

How does this PR change Premake's behavior?

Existing behavior should be unaffected.

Anything else we should know?

There are a number of other fsanitize options that are supported by gcc/clang, but not by msc or visual studio. I did not add support for these, but can if it is desired.

Did you check all the boxes?

• Focus on a single fix or feature; remove any unrelated formatting or code changes
  • I did make a couple unnecessary format changes, but only in files I was already modifying and nothing major.
• Add unit tests showing fix or feature works; all tests pass
• Mention any related issues (put closes #XXXX in comment to auto-close issue when PR is merged)
• Follow our coding conventions
• Minimize the number of commits
• Align documentation to your changes

You can now support Premake on our OpenCollective. Your contributions help us spend more time responding to requests like these!

[samsinsane]

We're in the process of deprecating flags and don't allow new values to be added to it, instead can you create a new API? Perhaps sanitize with the type list:string - basically the same as flags just for the sanitizer options.

[englercj]

Removed the flags and added a new sanitize API.

[englercj]

Anything else need to be changed here?

[nickclark2016]

In general, I'd say it looks good. As an aside, I see you added "address" sanitizer to GCC (and by proxy clang). What about fuzzer on Clang? It should be supported as well.

[englercj]

Requested changes have been made.

[nickclark2016]

fuzzer = 2022
asan = 2019

[nickclark2016]

LGTM. Leaving open for comments by @starkos or @samsinsane (or anyone else) for a few days, then I'll close. Thanks!

[nickclark2016]

Something I just noticed, for consistency with the API, I'll add a follow on to make the arguments lower case to be consistent with the rest of the API.

[englercj]

Ah, sorry. They were originally flags which use CamelCase so I had followed that pattern. Forgot to change casing when I switched to a new API.

[nickclark2016]

No worries. I approved the merge, it's on me.