Container kill on kuadrant-operator with extensions enabled

# Add Chaos Test for Socket File Persistence During Container Termination

## Description
Need to verify the behavior of Unix domain sockets in `emptyDir` volumes when containers are forcefully terminated. We've identified a potential issue where socket files might persist after SIGKILL, affecting container restarts within the same pod. Also see Kuadrant/kuadrant-operator#1554 .

## Test Plan
Use Chaos Mesh to simulate container termination scenarios in a test environment:

1. Deploy operator with extensions
2. Configure Chaos Mesh experiment for pod-kill
3. Assert no error messages and kuadrant-operator resumes successfully.

## Environment Requirements
- Chaos Mesh installed
- Access to pod logs and filesystem
- Ability to monitor container restarts

No file or existing test entry point is named in the issue. Start by locating the testsuite's operator-with-extensions deployment and its Chaos Mesh integration, then run a pod-kill experiment with the required environment; done means the operator resumes successfully without error messages after termination.

Written by the indexing model from the issue text.