Namespace Support

**Is your feature request related to a problem? Please describe.**
- Teams A should be allowed to manage & access App A ONLY, not App B, App C neither
- Teams B should be allowed to manage & access App B ONLY, not App A, App C neither
- Teams C should be allowed to manage & access App C ONLY, not App A, App B neither

**Describe the solution you'd like**
This is the purpose of Namespaces in K8S.

**Describe alternatives you've considered**
The only other option would be to create a new ASA instance.

**Additional context**
see [https://github.com/Azure/Azure-Spring-Apps/issues/20](https://github.com/Azure/Azure-Spring-Apps/issues/20)

Start by reading the Namespace Support request and the linked Azure/Azure-Spring-Apps issue #20, then review how Kubernetes namespaces provide team-level isolation. No files, tests, or entry points are identified; done would require an agreed design and implementation that limits each team's access to its own applications without requiring separate ASA instances.

Written by the indexing model from the issue text.