Partial & on demand SDK generation for specific needs

### 🧩 Name of the Activity

Partial SDK generation for the specific needs

### 🎯 Goal of this Activity

Enable on-demand SDK creation that only includes a subset of APIs tailored to the specific needs of a customer. This will reduce package size, simplify consumption, and improve developer productivity by exposing only the relevant APIs.

### 🌟 Champion Scenarios

Here is the scenarios:

- the SDK users only needs read-only APIs for a monitoring workload, and doesn’t want the overhead of write or admin APIs.

- A mobile application requires a lightweight SDK with only a few frequently-used APIs to reduce binary size and improve performance.

- A partner solution integrates with Azure but only relies on a limited set of APIs from different packages; generating a customized SDK to simplify onboarding.

- Better leverage AI-assisted generation to help customers describe their requirements and automatically generate the target SDK or 'code of Helper'.

### 🔧 How is this Activity Done Today?

Today we can only generate the entire package containing all APIs for a service, regardless of customer needs.
This leads to larger packages, unnecessary dependencies, and a higher learning curve for developers.

### 🛠️ Tools Needed to Support This Activity

- SDK Generation Framework Enhancements
- Client.tsp improvement for Configuration/Selection
- Testing and Validation Tools
- AI to help to convert the nature language into the demand of the SDK.

Start by reviewing the Client.tsp improvement request alongside the SDK Generation Framework Enhancements and the testing and validation tools mentioned in the issue. Done means supporting configurable, partial SDK generation for selected APIs, with validation that the generated package meets the requested scope.

Written by the indexing model from the issue text.