mgmt, use separate entry points for premium samples

[XiaofeiCao]

• emitter part for mgmt premium, keep premium samples in individual packages, instead of moving under azure-resourcemanager Azure/azure-sdk-for-java#47621
• autorest PR: sync core library https://github.com/microsoft/typespec/pull/9845 Azure/autorest.java#3298
• sync SDK PR looks good: [Automation] Generate SDK based on TypeSpec 0.40.0 DEV Azure/azure-sdk-for-java#48179

Summary

Replace AzureResourceManager with SDK-specific XXManager as the entry point in Fluent Premium samples.

Previously, premium samples were generated with AzureResourceManager as the entry type and then moved to sdk/resourcemanager/azure-resourcemanager/samples by the downstream generate.py script. This change makes premium samples use the corresponding XXManager (e.g., ComputeManager, StorageManager) directly, so samples can stay in their own SDK location.

Before vs After

// Before: premium sample used AzureResourceManager
void sampleMethod(com.azure.resourcemanager.AzureResourceManager azure) {
    azure.storageAccounts().manager().serviceClient().getStorageAccounts().list();
}

// After: premium sample uses SDK-specific manager
void sampleMethod(com.azure.resourcemanager.storage.StorageManager manager) {
    manager.serviceClient().getStorageAccounts().list();
}

Will update generate.py when this got shipped.

[github-actions]

All changed packages have been documented.

• ✅ @typespec/http-client-java

Show changes

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

mgmt, use separate entry points for premium samples

[azure-sdk]

You can try these changes here

🛝 Playground	🌐 Website	🛝 VSCode Extension