[Doc] Update README for aaw-argocd-manifests

[vexingly]

trafficstars

• [ ] How are these manifests deployed into dev/prod (i.e. what is the general workflow to update manifests and make releases into dev/prod)?
• [ ] How are these repos "bootstrapped"? E.g.
• [ ] Which manifests correspond to which repositories? A simple table that maps folder paths to repositories is probably sufficient, we just need a clear mapping of what all is being deployed. Additional detail can be contained in each specific repo's README. E.g.

Manifests Folder	Git Repository
/daaas-system/profiles-controller/	https://github.com/StatCan/aaw-kubeflow-profiles-controller
...	...

• [ ] Bonus points: it would be cool to have a diagrams as code diagram(s) here to show what all is deployed out of this repo. There is probably a way to use the Python kubernetes client to programmatically generate the equivalent of kubectl get argocd -A and (for example) kubectl get application -n daaas-system so that the .py file with the diagram source code can dynamically update if new deployments are added.