Enable Address Sanitizer in nightly builds

We regularly run our testsuite on binaries that built with enabled Address Sanitizer and enabling was useful - some issues were catched. Unfortunately our testsuite does not cover all user scenarios and it would be cool to provide binaries with enabled ASAN to users. It will help us to raise missed issues in Tarantool. ASAN immediately crashes executable as soon as wrong memory access detected and ASAN may downgrade overall application performance. Due to these reasons we cannot enable ASAN in released build, but enabling it in nightly build can be a compromise.

Discussed ticket with @Totktonada. He is afraid that users may use nightly builds in production and enabling ASAN may have negative impact for them. We decided to know do we have such users and estimate number of instances with nightly builds in production using Tg community chat and feedback statistics.

TBD: UBSan, Thread sanitizer.

Projects that enabled ASAN in nightly builds:

• rspamd https://rspamd.com/
• Mozilla Firefox https://firefox-source-docs.mozilla.org/tools/sanitizer/asan_nightly.html

"Typical slowdown introduced by AddressSanitizer is 2x.", see https://clang.llvm.org/docs/AddressSanitizer.html

GWP-ASan: Sampling heap memory error detection in-the-wild

Start by reviewing the existing nightly-build configuration and how the testsuite runs ASAN-enabled binaries. Use the Tg community chat and feedback statistics to estimate whether nightly builds are used in production, then assess the impact on nightly users while keeping released builds unchanged. Done means the nightly-build policy and implementation decision are documented.