Developer story
As a developer, I want to collect namespace resources and debug data within the CI E2E test script before the environment cleanup runs so that we have sufficient evidence for debugging, preventing the issue where the standard must-gather runs after resources are already deleted.

Description
Currently, the standard must-gather collection step executes after the hack/run-ci-e2e-test.sh script has finished.

However, if the tests succeed, the script proceeds to delete the Windows nodes (via TestWMCO/destroy) and clean up the WMCO operator/namespace resources before exiting.

Need to enable the collection of WMCO namespace resources  inside the test runner script, ensuring it executes immediately after the main test suite but strictly before the cleanup/teardown phase begins.

Engineering Details
Modify or verify hack/run-ci-e2e-test.sh.
Ensure the following resource collection logic is present before the if $SKIP_NODE_DELETION; then block where TestWMCO/destroy is called:

Acceptance Criteria

The inspection data is saved to ${ARTIFACT_DIR}/inspect.
Data collection occurs before Windows nodes are destroyed and before the WMCO deployment is cleaned up.
Inspect logs are available in the CI artifacts even when the test suite succeeds and cleans up after itself.