Remove use of azure next link

[AlitzelMendez]

Fixing breaking change caused by: Azure/typespec-azure#1886

Cadl Ranch Contribution Checklist:

• I have written a scenario spec
• I have meaningful @scenario names. Someone can look at the list of scenarios and understand what I'm covering.
• I have written a mock API
• I have used @scenarioDocs for extra scenario description and to tell people how to pass my mock api check.

[changeset-bot]

🦋 Changeset detected

Latest commit: b4d04f2

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@azure-tools/cadl-ranch-specs	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[weidongxu-microsoft]

@tadelesh Does TCGC at present handle the 2 nextLink annotation the same way?
If yes, I guess we can remove it here.

@AlitzelMendez I assume this PR depends on the merge on your typespec-azure-core PR? Azure/typespec-azure#1886

[tadelesh]

@tadelesh Does TCGC at present handle the 2 nextLink annotation the same way? If yes, I guess we can remove it here.

@AlitzelMendez I assume this PR depends on the merge on your typespec-azure-core PR? Azure/typespec-azure#1886

yes. there should be no impact for tcgc result as long as getPagedResult in core give the right result.

[weidongxu-microsoft]

Got it. So this PR would be read-to-merge after the PR to typespec-azure get merged.

[AlitzelMendez]

@tadelesh Does TCGC at present handle the 2 nextLink annotation the same way? If yes, I guess we can remove it here.

@AlitzelMendez I assume this PR depends on the merge on your typespec-azure-core PR? Azure/typespec-azure#1886

I would prefer if we can merge this first so I can have a green build in my other pull request, as we are running the E2E it fails as we are removing something that is still use in here

@markcowl could you please take a look? 😄

[markcowl]

@tadelesh @weidongxu-microsoft Because we verify cadl-ranch as part of ci checks in typespec-azure, this PR has to be merged before removing the decorator there. Can one of you or the other code owners approve this?

[weidongxu-microsoft]

approved and merged