Rendered Manifests branches should be a reflection of the Trunk

[christianh814]

When Kargo is set up to use the rendered manifest pattern, the branch it creates should be a reflection of the trunk. Example, Kargo would do the equivalent of:

1. Run kustomize set image in the given path on main (or specified trunk)
2. Commit that to main
3. Render the manifests to env/dev (or specified branch)

It's understood that this causes a "subscription loop", but after talking to @jessesuen - there might be a few ways to solve that so I'm opening this issue for posterity.

[krancour]

I will put some thought into this, but I think this creates other problems besides the subscription loop.

[krancour]

It seems this isn't proving to be as much of a sticking point for people as we may have feared it might be.

If it is, there's an sensible and easy pattern-based approach to solving for it: See #1119