See if we can modify swagger pagination definition so we get nextpage methods for free

[maririos]

If for whatever reason we can't on the service side, see if we can with transforms.
Also, undo this =>#18351 (comment)

[maririos]

See #18351 (comment)

[maririos]

The service is looking into adding showStats to the nextlink property. Once that is enabled, the fix in the swagger is easier for all languages.
For now .NET will do transforms

[maririos]

All pagination is now done automatically. Will move this issue for next milestone to keep following up so eventually we can remove the transforms in .NET

[maririos]

Service issue: https://msazure.visualstudio.com/Cognitive%20Services/_workitems/edit/9467692

[maririos]

Giving it a try in the swagger so we can remove the transforms on each language.
Draft PR Azure/azure-rest-api-specs#13615

[maririos]

After trying different approaches, the way the other languages are generating pageable, they depend on properties like value or items inside the response. The way TA works is that the whole response object is the one that is pageable and although .NET can handle this, the other languages can't.
So sadly, I'm going to have to close this issue and leave the transformations in the .NET autorest.md file :(