.zarf-state.yaml could use a bit more robustness

[YrrepNoj]

Two potential improvements on the current condition of the .zarf-state.yaml file.

1. Add a check (and warning log / confirmation dialog if not in --confirm) that a .zarf-state.yaml file already exists.

2. Right now the code only checks for a .zarf-state.yaml file in the current directory. This can create several issues, most of them revolving around the fact that we will be leaving behind lingering state files (zarf destroy only removes the state file if it's in the same directory you ran the command from) and the fact that if we init in one directory and switch directories before the zarf deploy command we will no longer be able to find the state file to reference which leads to an unclear set of logs.

This can be replicated by running the following commands:
./zarf init
mkdir testdir && cd testdir
../zarf destroy --confirm
ls -la ../.zarf-state.yaml -> it is still there after it was supposed to be destroyed.

[jeff-mccoy]

this is a valid point, I wouldn't be opposed to just doing an /etc/zarf thing instead, might actually be cleaner to put all state things there instead. Thoughts?

[YrrepNoj]

This will get resolved by #153