ArgoCD app with kustomize helm - helm resources deploy to default namespace

This is with ArgoCD v2.4.2 with `--enable-helm` for the kustomize renderer.

With a kustomization containing a chart, e.g.
```yaml
helmCharts:
- name: mychart
version: 1.0.0
repo: https://my.repo
releaseName: myrelease
includeCRDs: false
valuesInline: {}

resources:
- myresources.yaml
```

and an app
```yaml
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: myapp
namespace: argocd
spec:
destination:
namespace: mynamespace
...
```
the result is that resources in `myresources.yaml` end up in the `mynamespace` namespace, but resources from `mychart` end up in the `default` namespace.
This can be solved by explicitly adding the namespace specification to the kustomization. However, this reduces the reusability and can be a source of confusion with two places to specify the namespace.
I could not find an existing issue describing this.

Reproduce the report with the shown kustomization, myresources.yaml, and Argo CD Application manifest, using ArgoCD v2.4.2 with --enable-helm. Compare the namespaces assigned to resources from myresources.yaml and mychart; done means chart resources follow the Application destination without requiring a duplicate namespace in the kustomization.

Written by the indexing model from the issue text.