manifest-generate-paths does not work for absolute path that include ../

When using manifest-generate-paths with absolute paths that include ../ the webhook does not trigger an application refresh.

i.e. if you have something like this:
```
argocd.argoproj.io/manifest-generate-paths: /services/service1/some-values.yaml;/services/service1/../service2/some-other-values.yaml;
```
a refresh will only be triggered when this file changes:
/services/service1/some-values.yaml
but not this file:
/services/service2/some-other-values.yaml;

a workaround was to resolve the ../ before annotating i.e. to do this:
```
argocd.argoproj.io/manifest-generate-paths: /services/service1/some-values.yaml;/services/service2/some-other-values.yaml;
```

I might add that this was also a multi source app

Start at the manifest-generate-paths handling and follow how annotated paths reach the webhook-triggered application refresh, using the absolute path with ../ and the multi-source setup described here. Confirm that changes to both normalized target files trigger refreshes, while preserving the existing behavior for already-resolved paths.

Written by the indexing model from the issue text.