Azure: Gather coredumps
    
    Applications may crash.
    If a crash happens on a remote system during CI run it's sometimes
    very hard to understand the reason. The most important means to
    analyze such is a stack trace. It's also very important to check
    whether there was a core dump or not, even a test passed.
    
    For Docker environment, the core dumps are collected by the host's
    systemd-coredump, which knows nothing about such containers (for
    now). To build an informative thread stack trace debuginfo packages
    should be installed. But they can't be installed on the host OS
    (ubuntu), That's why after all the tests completed an additional
    container should be up and the host's core dumps and host's journal
    should be passed into it.
    
    Even if there weren't enough debuginfo packages at CI-runtime, the
    core dump could be analyzed locally later.
    
    Fixes: https://pagure.io/freeipa/issue/8251
    Signed-off-by: Stanislav Levin <slev@altlinux.org>
    Reviewed-By: Alexander Bokovoy <abokovoy@redhat.com>
    Reviewed-By: Rob Crittenden <rcritten@redhat.com>