BUILD/CONFIG: Introduce Address Sanitizer flag option

[ivankochin]

What

Introduces --enable-asan option which checks the Address Sanitizer availability and passes corresponding flags during compilation and linkage.

Why

Address Sanitizer is significantly faster then Valgrind and can detect more types of memory errors. For details go to the link: https://github.com/google/sanitizers/wiki/AddressSanitizerComparisonOfMemoryTools

Testing with GCC-7.2.0 on RHEL 7.6 detected false-positive buffer underflow errors during ucs_container_of call.
Testing with GCC-11 on Ubuntu-22.04 detected the following issues:

• TEST/UCT/MD: Prevent rkey buffer overflow #9518
• UCP/WIREUP: Define UCT_MD_FLAG_INVALIDATE_RMA description #9527
• TEST/UCP: Meet aligned_alloc requirements for requested size #9534

So it is important to test with fresh OS/compiler.

TODO:

• Define ASAN_OPTIONS=protect_shadow_gap=0 if cuda support enabled. See details here: asan: problem calling NVIDIA CUDA libraries google/sanitizers#629
• libcuda causes false positive leaks, consider creation lsan.supp (with one string: leak:libcuda) and passing LSAN_OPTIONS=suppressions=<path_to_lsan.supp> if cuda is enabled.
• If cuda leaks are suppressed for ASAN, CUDA can be tested through compute sanitizer.
• UCM is disabled if ASAN is enabled, and therefore rcache is disabled too. Can UCM or rcache be used with ASAN?

[ivankochin]

CUDA failure example (ASAN_OPTIONS=protect_shadow_gap=0 is set):