Zarf v0.14.0 gets into a broken state after zarf destroy

[RothAndrew]

Sometimes, usually after a zarf destroy, the .zarf-state.yaml and $HOME/.git-credentials files will get into a bad state, where the IP address / hostname is not present in the configuration, and zarf package deploy fails because it doesn't know where to push the docker images. This issue is resolved in v0.15.0 and can be mitigated on v0.14.0 by deleting .zarf-state.yaml and $HOME/.git-credentials (assuming there isn't other non-zarf stuff in it) after running zarf destroy.

[RothAndrew]

Since Zarf is still changing quite rapidly while it is in beta, signified by its version being v0.x, we aren't ready to start doing support branches to patch previously released versions. Users experiencing this issue are encouraged to upgrade to a later version of Zarf that isn't affected.