Description of problem:

There are some intermittent failures in the MachineConfigNode origin tests due to a lack of cleanup in one of the tests. When

1. the `Should properly update the MCN from the associated MCD` test runs before the `Should have MCN properties matching associated node properties for nodes in default MCPs` test AND
2. both tests target the same worker node,

the `Should have MCN properties matching associated node properties for nodes in default MCPs` test will fail due to the desired config version being set to a test value for the scope impersonation test.

Version-Release number of selected component (if applicable):

4.19

How reproducible:

Intermittent. Runs of the MCN tests will fail under certain conditions.

Steps to Reproduce:

See a failed job here: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-ipv6-techpreview/1913772445207105536

Actual results:

MCN test fails with the following error message:

I0420 04:30:59.561590 108434 helpers.go:379] MCN spec desired config version 'rendered-worker-test' does not match node desired config version 'rendered-worker-5227735aa03d23497dbec1900d4f17c9’.

Expected results:

`Should have MCN properties matching associated node properties for nodes in default MCPs` test should be stable and `Should properly update the MCN from the associated MCD` test should properly cleanup.

Additional info:

N/A