Making AppSource created ArgoCD Applications Project Scoped

# Summary
Thank you to @keithchong for inspiring this fix.

Because ArgoCD applications are actually CRDs within the cluster where a team's ArgoCD instance was installed — all applications need have to be globally unique names. This is related to an ArgoCD [issue](https://github.com/argoproj/argo-cd/issues/3709) requesting that ArgoCD applications be somehow project scoped, however the AppSource controller workflow should not wait for ArgoCD as a whole to be changed. Instead, the name of the ArgoCD Application will be \.\.\

# Motivation

The appsource controller promotes its utility across multiple clusters, not just the one where the ArgoCD instance may be installed. With this updated syncPolicy we can ensure that applications are being made within their own namespaces, no matter what cluster they're being requested from.

# Proposal
Create ArgoCD Applications with the name format \.\.\

Locate the AppSource controller code that creates ArgoCD Applications and inspect how the application name and sync policy are currently formed. Confirm the generated name follows .. and verify applications remain unique across clusters and namespaces.

Written by the indexing model from the issue text.