Add a `--skip-teardown-upon-failures` flag allowing deep dive in the environment to uncover the root cause of an issue

Potential usages for the Github CI of the operator:

```
- name: Dump Diagnostics
if: failure()
run: |
mkdir -p diagnostics
kubectl get events -A > diagnostics/events.txt
kubectl logs -n my-namespace -l app=my-operator > diagnostics/operator.log
kubectl get pods -A -o wide > diagnostics/pods.txt
# ... specific describes ...
- name: Upload Artifacts
if: failure()
uses: actions/upload-artifact@v4
with:
name: diagnostics-dump
path: diagnostics/

```

Start with the GitHub CI usage shown in the issue and trace how teardown is triggered after a failure. Define the new flag's behavior so the environment remains available for diagnostics, then verify the kubectl collection and actions/upload-artifact steps can run before teardown.

Written by the indexing model from the issue text.