Consider whether we need to check if maxpagesize should be reinjected

[JoshLove-msft]

We currently reinject maxPageSize, but it's possible the nextLink URL would already have this included from the initial request. It seems not worth having a runtime check, but the spector scenario is now failing in the Azure repo. Filing for tracking.

[jorgerangel-msft]

Sort of related to this, or at least, something we should also keep in mind if we tackle this #9246

[jorgerangel-msft]

@radhgupta fyi, we might need to implement this runtime check since you are running into this as part of the content safety migration

[JoshLove-msft]

I wonder if we should instead use https://azure.github.io/typespec-azure/docs/libraries/azure-core/reference/data-types/#Azure.Core.Legacy.parameterizedNextLink for maxPageSize for services that expect it to be reinjected. I will follow up to see what the guidance is here.