test/common: abort on detected leaks

Most of the AddressSanitizer logs are great in regards
to reported incorrect usage of memory.
Unfortunately LeakSanitizer reports just the leaks.
Having more details how exit of the application happened,
is useful to get a starting point.

For example spdk_perf app has multiple exit()s that
are used at points where no cleanup was done.
Adding abort_on_error will generate a core dump with
a backtrace pointing to the specific exit().

Abort now replaces returning specific exitcode.
It was originally a way to differentiate between
expected exit and ASAN exit. Abort is never expected,
even in NOT() tests, so exitcode is no longer needed.

Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
Change-Id: Idc5ea003d0c0860294a564e1ad770471bb35bc42
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/20735


Reviewed-by: Shuhei Matsumoto <smatsumoto@nvidia.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Konrad Sztyber <konrad.sztyber@intel.com>
Reviewed-by: Michal Berger <michal.berger@intel.com>