handled paging parameter casing

[radhgupta]

This pull request improves the handling of page size parameter names in the C# HTTP client generator to ensure correct casing and compatibility with previous contract versions. The changes introduce logic to preserve parameter casing from the previous contract when available and to normalize common variants (like "maxpagesize") to the standard "maxPageSize" otherwise. Comprehensive tests are added to verify this behavior.

Resolves: Azure/azure-sdk-for-net#54468

[github-actions]

No changes needing a change description found.

[jorgerangel-msft]

Could we also make sure to run the regen preview script?

[radhgupta]

Could we also make sure to run the regen preview script?

@jorgerangel-msft I do see changes when we run regen preview the changes are that the Client now has camelCased maxPageSize Parameter.
The changes are reflected in following SDK Azure.Ai.Language.TextAuthoring, Azure.Analytics.Defender.Easm, Azure.Developer.LoadTesting and Azure.Analytics.OnlineExperimentation

[jorgerangel-msft]

Could we also make sure to run the regen preview script?

@jorgerangel-msft I do see changes when we run regen preview the changes are that the Client now has camelCased maxPageSize Parameter. The changes are reflected in following SDK Azure.Ai.Language.TextAuthoring, Azure.Analytics.Defender.Easm, Azure.Developer.LoadTesting and Azure.Analytics.OnlineExperimentation

As long as these changes are expected, then it should be okay. For the libraries that haven't GA'd I'm assuming we are "fixing" the parameter to be maxPageSize right? For the library that has GA'd, we are respecting the casing from the last GA version?

[radhgupta]

Could we also make sure to run the regen preview script?

@jorgerangel-msft I do see changes when we run regen preview the changes are that the Client now has camelCased maxPageSize Parameter. The changes are reflected in following SDK Azure.Ai.Language.TextAuthoring, Azure.Analytics.Defender.Easm, Azure.Developer.LoadTesting and Azure.Analytics.OnlineExperimentation

As long as these changes are expected, then it should be okay. For the libraries that haven't GA'd I'm assuming we are "fixing" the parameter to be maxPageSize right? For the library that has GA'd, we are respecting the casing from the last GA version?

Exactly!!! The casing only applies if paging parameter is "maxpageszie" and the library is not GA'd

[JoshLove-msft]

Could we also make sure to run the regen preview script?

@jorgerangel-msft I do see changes when we run regen preview the changes are that the Client now has camelCased maxPageSize Parameter. The changes are reflected in following SDK Azure.Ai.Language.TextAuthoring, Azure.Analytics.Defender.Easm, Azure.Developer.LoadTesting and Azure.Analytics.OnlineExperimentation

As long as these changes are expected, then it should be okay. For the libraries that haven't GA'd I'm assuming we are "fixing" the parameter to be maxPageSize right? For the library that has GA'd, we are respecting the casing from the last GA version?

Exactly!!! The casing only applies if paging parameter is "maxpageszie" and the library is not GA'd

Can we update this file with this scenario - https://github.com/microsoft/typespec/blob/main/packages/http-client-csharp/generator/docs/backward-compatibility.md