addr2line stack trace resolver deterimental in MariaDB-backup and MSAN/ASAN builds

From https://github.com/MariaDB/buildbot/pull/933, in a MSAN/ASAN test environment, the addr2line was so high in memory utilization (anon-rss:14320664kB) that it was the pick of the OOM killer to resolve the OOM situation.

It addition to its harmful effects, it resolution is of such a poor quality compared to a) the implementation of the sanitizers themselves, b) the core dump and gdb resolution that is most common for these environments that use these instrumented builds.

A simple solution is to default stack-trace to 0 for the ASAN/MSAN builds.

MariaDB-backup also forces the enabling of stack-trace. Disabling this unconditionally reduces the risk of a user operational impact if a stack trace starts in a mariabackup critical locked period.