Allow for data key in Introspection diff

[tvvignesh]

Description

Addressing feedback from @AllexVeldman here: #2054 (comment) with respect to allowing optional data key during introspection.

Fixes #2054 (comment)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist:

• I have followed the CONTRIBUTING doc and the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/theguild/graphql-inspector/6opKAXa2TjnKX46ffHnfqMc9vQLD
✅ Preview: https://graphql-inspector-git-fork-tvvignesh-introspect-8ab149-theguild.vercel.app

[AllexVeldman]

@kamilkisiela Is there anything we need to do to advance this PR?