Flaky tests because of CRD deletion

[csviri]

Quite often see this error:
https://github.com/operator-framework/java-operator-sdk/actions/runs/13768182946/job/38499882350?pr=2722

Usually for E2E tests. Would be nice to make CRD deletion feature more robust. (Or opt in for the e2e tests)

[csviri]

@xstefank I was thinking that if the CRD is not deleted or we cannot delete with a timeout it could be just a warning in the logs (so we delete it with kinda best effort, but don't fail the tests because of that). WDYT?