Switch to use stable SWAPI endpoint in examples

[eddeee888]

Description

https://github.com/graphql/swapi-graphql recently moved to a new endpoint, so this PR updates the endpoint references.
Some tests were failing because they were using the old endpoint

Type of change

• Fix CI

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6dae7a6

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[github-actions]

🚀 Snapshot Release (alpha)

The latest changes of this PR are available as alpha on npm (based on the declared changesets):

Package	Version	Info
@graphql-codegen/client-preset	4.6.0-alpha-20250117130226-6dae7a681527f271cea967ed9785bd74c7aa7104	npm ↗︎ unpkg ↗︎

[github-actions]

💻 Website Preview

The latest changes are available as preview in: https://61c4006d.graphql-code-generator.pages.dev

[saihaj]

ohh i would move to this is the stable endpoint. Folks try to point to the neltify thing but that's internal only (yes people find it) but this endpoint you can be certain will be there :)

https://graphql.org/graphql/

meant to request changes

[eddeee888]

Thanks @saihaj ! I've updated to https://graphql.org/graphql/, and we worked through the endpoint issues outside of this PR. This is now working!

I'll merge this first to unblock CI & rebase a few PRs - if there's other comments, happy to implement as subsequent PRs