ci: reset failed systemd unit on OOM test

[lrascao]

On centos stream9, when running the events oom test, systemd goes into a degraded state causing subsequent tests to fail, resetting the failed unit after the test fixes this. Not sure if this is the right fix but hopefully it's a step in the right direction to getting CI back to green.

$ RUNC_USE_SYSTEMD=true bats -t tests/integration/events.bats
$ [root@localhost runc]# systemctl --failed
  UNIT                                      LOAD   ACTIVE SUB    DESCRIPTION
● runc-cgroups-integration-test-29550.scope loaded failed failed libcontainer container integration-test-29550

several tests then start failing:

$ RUNC_USE_SYSTEMD=true bats -t tests/integration/ps.bats
# (in test file tests/integration/ps.bats, line 60)
#   `[[ "${lines[1]}" =~ [0-9]+ ]]' failed
# runc spec (status=0):
#
# runc run -d --console-socket /tmp/bats-run-85oCGW/runc.mWta7t/tty/sock test_busybox (status=0):
#
# runc state test_busybox (status=0):
# {
#   "ociVersion": "1.1.0-rc.1",
#   "id": "test_busybox",
#   "pid": 26325,
#   "status": "running",
#   "bundle": "/tmp/bats-run-85oCGW/runc.mWta7t/bundle",
#   "rootfs": "/tmp/bats-run-85oCGW/runc.mWta7t/bundle/rootfs",
#   "created": "2023-04-02T22:19:42.912423842Z",
#   "owner": ""
# }
# runc ps test_busybox -e -x (status=0):
#     PID TTY      STAT   TIME COMMAND
# /root/runc/tests/integration/ps.bats: line 60: lines[1]: unbound variable
ok 4 ps after the container stopped

systemctl reset-failed

[lrascao]

rebased on top of #3788, ci/centos-stream-9 is green now

[lrascao]

rebased back onto main, CI will now fail as #3788 is missing now

[kolyshkin]

Thank you for your contribution! This was addressed by #3835 which does something like this and a bit more.

[kolyshkin]

Thank you for your contribution! This was addressed by #3835 which does something like this and a bit more.

Sorry, I mean #3782