fix: delete CRD only after all tests in the class pass

[xstefank]

Fixes #2928

[xstefank]

@csviri I wasn't sure if you mean after all tests or after test class, so I did a after a test class first, but I can move it to after testsuite.

[Copilot]

Pull request overview

This PR fixes issue #2928 by deferring CRD (Custom Resource Definition) deletion from after each test method to after all tests in a class have completed. Previously, CRDs were deleted after each test, causing issues when a deleted CRD remained in a "deleting" state and caused subsequent tests to fail.

Changes:

• Added import for KubernetesClientBuilder to enable creating a fresh Kubernetes client during cleanup
• Introduced a new static inner class CrdCleanup that implements ExtensionContext.Store.CloseableResource to handle cleanup at the class scope level
• Moved CRD deletion logic from the after() method (called after each test) to the CrdCleanup.close() method (called when the class scope closes)
• Registered CrdCleanup in the extension context store at class scope to ensure it's invoked once per test class
• Improved exception handling during CRD deletion with a try-catch wrapper
• Clarified variable naming from kubernetesClient to infrastructureKubernetesClient for better code readability