fix: Invalid context on GraphQL request errors

[jmccance]

📜 Description

Fixes SentryNetworkTracker to add an object for GraphQL context instead of a string.

💡 Motivation and Context

Fixes #4560.

💚 How did you test it?

• Added a unit test to SentryNetworkTracker to verify that the context object has a graphql key that looks the way we expect it to look.
• Tested the change locally in our app and verified that the warning documented in enableGraphQLOperationTracking attaches invalid context to network errors #4560 doesn't appear after this change and the new graphql context section does.

📝 Checklist

You have to check all boxes before merging:

• I added tests to verify the changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• I updated the docs if needed.
  • I don't think there are any docs for this that need updating.
• I updated the wizard if needed.
  • This change shouldn't affect project setup
• Review from the native team if needed.
  • I don't think so, but will wait for someone to tell me.
• No breaking change or entry added to the changelog.
• No breaking change for hybrid SDKs or communicated to hybrid SDKs.

🔮 Next steps

Ideally I'd like to include the GraphQL operation name in the client tags. This would help us identify which actual calls are causing the most errors — currently we have one issue with tens of thousands of events in it and no good way to figure out which calls are the problem.

But for now I'm just making sure we're able to see the operation correctly on network errors.

[jmccance]

Following instructions from check-tooling-versions.sh:

clang-format version mismatch, expected: 19.1.3, but found: 19.1.4. Please run make init to update your local dev tools. This may actually upgrade to a newer version than what is currently recorded in the lockfile; if that happens, please commit the update to the lockfile as well.

Let me know if you don't want this change in this PR, but it was preventing me from committing with the pre-commit hook in place.

[jmccance]

Not sure if there's anything special needed to get prettier names in the Sentry dashboard, or if that's necessary. Here's how this looks in a test event I generated with our app:

GraphQL and Operation Name would look more aligned with the Operating System context, but my hunch is these may be getting special treatment server-side since I don't see these strings in the sentry-cocoa project anywhere.