cirrus: ensure NOTIFY_SOCKET is properly unset for all tests

Podman uses this env toi do various things, we don't want the external
env to affect our tests here.

Signed-off-by: Paul Holzinger <pholzing@redhat.com>

Author: Luap99

contrib/cirrus/runner.sh

@@ -506,6 +506,9 @@ if [ "$(type -t $handler)" != "function" ]; then
     die "Unknown/Unsupported \$TEST_FLAVOR=$TEST_FLAVOR"
 fi
 
+# Unset NOTIFY_SOCKET based on: https://github.com/containers/podman/pull/27514#issuecomment-3529125596
+unset NOTIFY_SOCKET
+
 showrun $handler
 
 if [[ -n "$TRACER_PID" ]]; then

contrib/cirrus/setup_environment.sh

@@ -73,8 +73,6 @@ echo -e "\n# Begin single-use VM global variables (${BASH_SOURCE[0]})" \
     done <<<"$(passthrough_envars)"
 ) >> "/etc/ci_environment"
 
-# Unset NOTIFY_SOCKET based on: https://github.com/containers/podman/pull/27514#issuecomment-3529125596
-unset NOTIFY_SOCKET
 # This is a possible manual maintenance gaff, i.e. forgetting to update a
 # *_NAME variable in .cirrus.yml.  check to be sure at least one comparison
 # matches the actual OS being run.  Ignore details, such as debian point-release