Improve OOMKilled Visibility

[Banana-Cultist]

As seen in issues #26701 and #25990, discovering whether a container has been OOMKilled doesn't seem to be very well known to users.

To address this, this PR adds an example of inspecting a container for the OOMKilled attribute to the podman inspect docs.

However, in scenarios where a container is automatically restarted, the podman inspect data will get wiped. In these cases, an OOMKilled attribute has been added to the container died event. This way, podman events can be a more persistent source of this information.

In short, this PR:

• Adds an OOMKilled attribute to the container died event
• Adds a system test for the above
• Updates documentation of podman inspect to include an example of inspecting a container for the OOMKilled label.

Fixes: #26701

Checklist

• Certify you wrote the patch or otherwise have the right to pass it on as an open-source patch by signing all
  commits. (git commit -s). (If needed, use git commit -s --amend). The author email must match
  the sign-off email address. See CONTRIBUTING.md
  for more information.
• Referenced issues using Fixes: #00000 in commit message (if applicable)
• Tests have been added/updated (or no tests are needed)
• Documentation has been updated (or no documentation changes are needed)
• All commits pass make validatepr (format/lint checks)
• Release note entered in the section below (or None if no user-facing changes)

Does this PR introduce a user-facing change?

Add OOMKilled attribute to container died event

[Honny1]

At first glance, LGTM. I have some doubts due to the related test failure, but since it’s only one failure, I re-ran the test to see if it’s flaky or needs more attention.

[packit-as-a-service]

[NON-BLOCKING] Packit jobs failed. @containers/packit-build please check. Everyone else, feel free to ignore.