The Zarf agent should not mutate git repos when there was no git repo specified on Zarf init about zarf HOT 1 OPEN

I would like to add to this that it would be nice to be able to use the internal image repository independently of the git repo mutation. Our use case is that we have a git repository solution already in place for out airgapped clusters, BUT we currently package up our cluster images and "manually" set them in place with ansible playbooks. It would be wonderful if we could simply use the image portion of the mutating web hooks and the dpeloyment of the secret to acces that internal repo. As it stands if i add a label for zarf.dev/agent: ignore, depending on what object we end up with some pods not having their request for an image mutated to point internally, and some do have the mutation but the internal repo secret may not be deploy into that namespace.

from zarf.