Support multiple namespaces in client library code generation

[srnagar]

Clear and concise description of the problem

Currently, code generators for .NET, Java and Python only support generating client library in a single namespace. Generators use the namespace defined in tspconfig.yaml and ignore the namespaces defined in TypeSpec. This works when we only have a single namespace.

However, there are cases where we need multiple namespaces in the generated library to allow different clients to be in different namespaces (for e.g. OpenAI and Search). So, the proposal is for generators to use the namespaces defined in TypeSpec as the namespaces in client libraries too and not use tspconfig.yaml.

More details on the proposal can be found here.

Checklist

• Follow our Code of Conduct
• Read the docs.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Spec

Beta Give feedback

1. Namespace refactoring Scenario tests Azure/cadl-ranch#758
   +0
   
2. Namespace refactoring TCGC Author doc Azure/typespec-azure#1722
   docs lib:tcgc +2
   

Implementation

Beta Give feedback

1. Namespace refactoring TCGC Implementation Azure/typespec-azure#1723
   lib:tcgc +1
   
2. Namespace refactoring Implementation Azure/autorest.java#2968
   +0
   
3. Namespace refactoring Implementation Azure/autorest.typescript#2877
   HRLC p0 +2
   
4. Namespace refactoring Implementation Azure/autorest.csharp#5124
   +0
5. Namespace refactoring Implementation Azure/autorest.go#1452
   +0
   
6. https://github.com/Azure/autorest.cpp/issues/404
7. https://github.com/Azure/typespec-rust/issues/130
8. Support multi namespaces Azure/autorest.python#2795
   +0
   
9. [tcgc] namespaces in TCGC Azure/typespec-azure#1604
   lib:tcgc +1