WebApps_ListHybridConnections operations is modeled as a single return type operation but should be modeled as pagable list return type operation

Simply this line - https://github.com/Azure/azure-rest-api-specs/blob/master/specification/web/resource-manager/Microsoft.Web/stable/2016-08-01/WebApps.json#L3250 should be the same as this line https://github.com/Azure/azure-rest-api-specs/blob/master/specification/web/resource-manager/Microsoft.Web/stable/2016-09-01/AppServicePlans.json#L593 .

As a result generated code has a single response value operation https://github.com/Azure/azure-sdk-for-net/blob/psSdkJson6/src/SDKs/WebSites/Management.Websites/Generated/IWebAppsOperations.cs#L2391 but should be generated as a pagable collection response. Currently developers cannot list all the hybrid connections for their websites.

Compare the operation at specification/web/resource-manager/Microsoft.Web/stable/2016-08-01/WebApps.json#L3250 with specification/web/resource-manager/Microsoft.Web/stable/2016-09-01/AppServicePlans.json#L593. Then inspect the generated IWebAppsOperations.cs entry at line 2391 to confirm the expected pagable collection shape. Done means the WebApps_ListHybridConnections operation generates a pagable collection response so developers can list all hybrid connections.

Written by the indexing model from the issue text.