Carlos wants to be able to run the pipelines and apps in different projects during the CI process so they can be isolated

Currently during the pipeline run, a CI version of the application is deployed into the dev/CI namespace to verify the image and the deploy logic. In some cases it is simpler if the workloads are separated between two projects - one for the pipelines and another for the apps.

This can be handled by exposing another parameter in the pipeline for the `app-namespace` that can be defaulted to the same namespace as the pipeline. In order for this to work, the new namespace will need to be created already and the `pipeline` SA must be given access to deploy resources into it.

This change allows for separation between the pipelines and the apps which can then be used to give developers different levels of access - view only for pipelines and admin for the dev. It also means network and authorization policies can be applied differently.

The downside is that the project where the apps are deployed might be used for the wrong purposes. The apps deployed to the CI/Dev project should not be used for any purpose other than to debug a failed build. If the developers want an environment to work with the deployed application they should really do it in a separate project that has been deployed via Argo.