[http-client-java] mgmt premium, fix sample entry point and serviceClient reference for autorest

[XiaofeiCao]

Bug

When generating premium mgmt samples from Swagger, we switched to use individual entry points in #9845. However, for multi-service scenario(appservice, resources, etc)

1. entry point now be the aggregated Manager, instead of the individual packages, e.g. There's no PolicyManager, but rather ResourceManager.
2. service client got separate too, instead of residing inside of the entry Manager. e.g. There's no ResourceManager.serviceClient().getPolicyDefinitions(), but rather ResourceManager.policyClient().getPolicyDefinitions().

Solution

We'll need
For 1. Add service-name config to api-specs.json, to allow for entry point discovery. E.g. ResourceManager instead of default PolicyManager. PR: Azure/azure-sdk-for-java#48490
For 2. We need secondary service client entry mapping. Fortunately, we already have metadata-suffix that we can use:
E.g. https://github.com/Azure/azure-sdk-for-java/blob/16fffda39d14c6fc6f3f24a972814c429d46c135/sdk/resourcemanager/api-specs.json#L18

Limitation

The fix is mainly for Swagger purpose. Might need a revisit for TypeSpec multi-service.
Will log an issue if we take this approach.

About this PR

• Generated sample code for domainregistration looks like:
  
• autorest PR: Sync PR https://github.com/microsoft/typespec/pull/10082, prepare typespec-java 0.43.2 and autorest.java 4.1.64 Azure/autorest.java#3307
• sync SDK PR: [Automation] Generate SDK based on TypeSpec 0.43.2 DEV Azure/azure-sdk-for-java#48493

[github-actions]

All changed packages have been documented.

• ✅ @typespec/http-client-java

Show changes

@typespec/http-client-java - fix ✏️

mgmt premium, fix sample entry point and serviceClient reference

[azure-sdk]

You can try these changes here

🛝 Playground	🌐 Website	🛝 VSCode Extension