fix(docs): Update iotagraphqlclient schema

[vivekjain23]

Description of change

This PR brings up the updation in the GraphQLClient doc to use the new schema.

Links to any relevant issues

fixes #7253

How the change has been tested

• Basic tests (linting, compilation, formatting, unit/integration tests)
• Patch-specific tests (correctness, functionality coverage)
• I have added tests that prove my fix is effective or that my feature works
• I have checked that new and existing unit tests pass locally with my changes

Release Notes

• Protocol:
• Nodes (Validators and Full nodes):
• Indexer:
• JSON-RPC:
• GraphQL:
• CLI:
• Rust SDK:
• REST API:

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
apps-backend	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 11, 2025 8:20am
rebased-explorer	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 11, 2025 8:20am
wallet-dashboard	✅ Ready (Inspect)	Visit Preview		Jun 11, 2025 8:20am

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
apps-ui-kit	⬜️ Ignored (Inspect)	Visit Preview		Jun 11, 2025 8:20am

[github-actions]

✅ Vercel Preview Deployment is ready!

View Preview

[Ginowine]

Just asking for clarification. Is there any reason you are not getting the gqlClient as you did in this PR? @vivekjain23

https://github.com/iotaledger/iota/pull/7256/files

[vivekjain23]

Just asking for clarification. Is there any reason you are not getting the gqlClient as you did in this PR? @vivekjain23

https://github.com/iotaledger/iota/pull/7256/files

I get the point. I started working on the utility function, then found the schema and types had not been updated, so I created the issue, solved it, and continued on the utility function issue, which resulted in the same changes in both PRS 😅.