GitOps should be file-location agnostic

[stealthybox]

@twelho mentioned on the aug12 developer call that the current GitOps implementation will destroy and re-create the VM if you move a manifest to a different location in the git repo.

It should be possible to re-organize manifests to wherever file paths you want in the git-repo.
As long as the unique information does not change (names/id's), ignite should be able to keep track of the object.

The internal catalog should key resources by their Group/Version/Kind/name or tuple of other UID's.
That should allow ignite to continue managing the same VM even if the file location of the manifest is moved by the user.

[stealthybox]

( If we ever intend to make the directory structure or filenames in the Git-repo significant to the meaning of the manifests these can be intentionally added to the identifying tuple of resources. )