Dump namespace if the namespace could not be cleaned up

[schrodit]

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:

/kind bug
/kind failing-test

What this PR does / why we need it:
The e2e testsuite performs a cleanup after each tests were namespaces are deleted.
If this cleanup fails the only thing that is currently logged is the client-go error which is most of the time not helpful as namespace deletion can be blocked by various resources that are still left/cannot be cleaned up.
If the tests are even executed successfully we do not get the namespace dump (DumpAllNamespaceInfo) which is very helpful when debugging such issues.

This PR adds the namespace dump even if all tests succeeded but the cleanup fails.

Example bug where test succeeded but the namespace cannot be deleted as of a stuck pod: #85541
Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

e2e-test-framework: add e2e test namespace dump if all tests succeed but the cleanup fails.

[k8s-ci-robot]

Hi @schrodit. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[schrodit]

/sig testing

[schrodit]

/assign @timothysc

[neolit123]

@schrodit best to prefix the release note (user facing change) with e2e-test-framework for better clarity.

/ok-to-test
/priority backlog
/lgtm
/assign @oomichi
to have a look too / potentially approve.

[schrodit]

@oomichi any update on this?

[timothysc]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: schrodit, timothysc

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• test/e2e/framework/OWNERS [timothysc]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment