Fix path parameter generation for cross-scope collection resources

[Copilot]

The management generator incorrectly promoted path parameters like subscriptionId and resourceProviderName to constructor fields in collection classes when they should remain as method parameters. This occurred for resources accessed across scope boundaries (e.g., ManagementGroup accessing per-subscription resources).

Changes

Added scope transition detection (HasScopeTransition)

• Detects when subscriptionId appears in path after non-subscription parent
• When detected, all intermediate path parameters remain as method parameters
• Prevents incorrect field promotion for cross-scope resource access

Added parameter-specific rules (ShouldParameterRemainAsMethodParameter)

• subscriptionId: method parameter when parent is not subscription-scoped
• resourceProviderName: always method parameter (filtering/scoping parameter)

Refactored scope checking (IsParentSubscriptionScoped)

• Extracted common subscription-scope checking logic

Example

For path /providers/Microsoft.Management/managementGroups/{managementGroupId}/subscriptions/{subscriptionId}/providers/Microsoft.Quota/groupQuotas/{groupQuotaName}/resourceProviders/{resourceProviderName}/quotaAllocations/{location}:

Before: subscriptionId, groupQuotaName, resourceProviderName as constructor parameters

internal SubscriptionQuotaAllocationsListCollection(ArmClient client, ResourceIdentifier id, 
    string subscriptionId, string groupQuotaName, string resourceProviderName)

After: All as method parameters

internal SubscriptionQuotaAllocationsListCollection(ArmClient client, ResourceIdentifier id)

public Task<Response<T>> GetAsync(string subscriptionId, string groupQuotaName, 
    string resourceProviderName, AzureLocation location, ...)

Aligns with autorest.csharp behavior. Fixes Azure.ResourceManager.Quota SDK generation.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>subscriptionId should be generated as method parameter</issue_title>
<issue_description>while onboarding Azure.ResourceManager.Quota to new mpg generator, subscriptionId was generated as client field in resourceCollection:

azure-sdk-for-net/sdk/quota/Azure.ResourceManager.Quota/src/Generated/SubscriptionQuotaAllocationsListCollection.cs

Line 50 in f9bc060

internal SubscriptionQuotaAllocationsListCollection(ArmClient client, ResourceIdentifier id, string managementGroupId, string subscriptionId, string groupQuotaName, string resourceProviderName) : base(client, id)

the expecting constructor should be

azure-sdk-for-net/sdk/quota/Azure.ResourceManager.Quota/src/Generated/SubscriptionQuotaAllocationsListCollection.cs

Line 36 in 81fdb88

internal SubscriptionQuotaAllocationsListCollection(ArmClient client, ResourceIdentifier id) : base(client, id)

The original logic of populating additional constructor parameter in autorest.csharp is https://github.com/Azure/autorest.csharp/blob/d93297d16162903b0f2647f890a5db99535e2009/src/AutoRest.CSharp/Mgmt/Output/ResourceCollection.cs#L81-L132

refine the mgmt generator to align with autorest.csharp</issue_description>

Comments on the Issue (you are @copilot in this section)

@live1206 `resourceProviderName` should be method parameter instead of client parameter as well https://github.com/Azure/azure-sdk-for-net/blob/f9bc06044da09ca30956c242c9eb887ce5833e05/sdk/quota/Azure.ResourceManager.Quota/src/Generated/GroupQuotasEnforcementStatusCollection.cs#L44

• Fixes subscriptionId should be generated as method parameter #53181

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.