[release-1.6] 🌱 test: add dynamic finalizer assertions for e2e framework

[adityabhatia]

Manual cherry-pick of #9970

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes # #9969

/area testing

[k8s-ci-robot]

Hi @adityabhatia. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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.

[adityabhatia]

Note: This PR doesn't contain the Kind conflict addressed here. IMO it also makes sense to cherry-pick that change, to avoid any namespaced name collisions?
I can create a 1.6 cherry-pick once this PR is merged, to avoid conflicts.
cc: @sbueringer

[sbueringer]

Note: This PR doesn't contain the Kind conflict addressed here. IMO it also makes sense to cherry-pick that change, to avoid any namespaced name collisions? I can create a 1.6 cherry-pick once this PR is merged, to avoid conflicts. cc: @sbueringer

Agree, thx! I'll cherry-pick the other one with the bot then a quick rebase on this PR should be fine (#10004)

[sbueringer]

Thx!

/lgtm
/approve

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 3b1a36f5cab9b5ed619518f61c68371d80ef5ae5

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sbueringer

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:

• OWNERS [sbueringer]

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