If an App doesn't come up due to node config issues we don't clean up

[cunningr]

Description

During testing of different interface types I noticed that if an App doesn't come up all the way to RUNNING due to node config issues, when we delete the pod, we don't clean up at all.

Expected Behavior

From any pod/container state we should be able to clean up the installed App container configuration on the device.

Actual Behavior

The app stays configured and installed on the device and required manual cleanup

Affected Version

err main branch :-)

Steps to Reproduce

1. Create a config with a network configuration that will prevent an IP being allocated (E.g. DHCP when not configured on the device)
2. Start the CVK and try to deploy a pod.
3. The app will not reach RUNNING. When trying to delete the pod CVK will not progress

A workaround seems to be to stop and restart the CVK instance. The initial pod discovery will discover a pod that should not exist and clean it up.

Checklist

• I have read the contributing guidelines
• I have verified this does not duplicate an existing issue