Assumes that `HelmRelease` and repo are defined in the same (`helm.yaml`) file

[abstrask]

It's currently assumed that HelmRelease and its repo (HelmRepository, OCIRepository or GitRepository) are defined in the same file (that is named helm.yaml).

However, there are good reasons why you may want to separate these, e.g. if deploying multiple releases from the same repository.

The best approach to fixing this, would probably be to not just look at (changed) helm.yaml files, but actually render kustomize.yaml files, and then select HelmRelease and the referenced repo within the rendered manifests.

This would also include any changes caused by Kustomize patches. Also, this might be a step towards transitioning into a general Kustomize diff tool?

However, how to determine which directories Kustomize should be run in? Any directory with a kustomize.yaml file? If so, that would still present a problem, when the release and repo are referenced in two different Kustomize files.

Or is it better to read a directory list from a config file in the root of the repo? This would also make it easy to exclude some manifest/directories from the diff tool.

It will be necessary to also solve #5, as it will no longer be reasonable to assume that only a single repository (of each kind) exists in all of the rendered manifests.