[WIP] Add API-Version update in Spector tests

[Copilot]

Thanks for assigning this issue to me. I'm starting to work on it and will keep this PR's description up to date as I form a plan and make progress.

Original issue description:

We need a new test in "azure-http-specs", in "azure/payload/pageable", that tests the following two scenarios:

Scenario 1

• First GET call, returns a pageable operation, where the nextLink has an api-version of v1
• The TypeSpec actually has an APIVersion of v2
• It's expected that when the SDK will call the nextLink to get page 2, the mock endpoint only works if the url includes "v2". If "v1" is received, the mockapi must fail saying that APIVersion should have been updated.

Scenario 2

• First GET call, returns a pageable operation, where the nextLink doesn't have an api-version
• The TypeSpec actually has an APIVersion of v2
• It's expected that when the SDK will call the nextLink to get page 2, the mock endpoint only works if the url includes "v2". If no api-version is received, the mockapi must fail saying that APIVersion should have been added.

Fixes #2825.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[iscai-msft]

Look at the copilot instructions again and redo this pr

[Copilot]

Look at the copilot instructions again and redo this pr

I've reviewed the copilot instructions and completely redone the PR following the guidelines. Added two new API-Version update test scenarios in azure/payload/pageable with proper @scenario/@scenarioDoc decorations and mockapi implementations that validate SDK behavior when nextLink has incorrect/missing api-version parameters. Commit: 2b280d7