Enable address sanitizer option `detect_stack_use_after_return`

[msimberg]

Currently the address sanitizer CI job added in #972 explicitly disables detect_stack_use_after_return (default is also off, but this is to protect from a change to the default). It seems like enabling this option leads to some tests simply failing (not with warnings from address sanitizer, but with segfaults etc.). E.g.:

        Start 128: tests.unit.modules.resource_partitioner.suspend_pool_external
128/230 Test #128: tests.unit.modules.resource_partitioner.suspend_pool_external ......................Subprocess killed***Exception:  66.66 sec

Investigate what is causing the problem and/or see if a newer version of sanitizers don't trigger this issue. It seems like this may be related to excessive memory usage by address sanitizer.