Feature Request: Plugin that Sends GraphQL Response Data to Inngest

[Inngest](https://www.inngest.com) makes it simple for you to write delayed or background jobs by triggering functions from events — decoupling your code from your application.

- You send events from your application via HTTP (or via third party webhooks, e.g. Stripe)
- Inngest runs your serverless functions that are configured to be triggered by those events, either immediately, or delayed.

Inngest brings the benefits of event-driven systems to all developers, without having to write any code themselves.

Inngest believes that:

- Event-driven systems should be easy to build and adopt
- Event-driven systems are better than regular, procedural systems and queues
- Developer experience matters
- Serverless scheduling enables scalable, reliable systems that are both cheaper and better for compliance

## The Plugin

A plugin that sends GraphQL response data as structured events to Inngest will help to effortlessly build event-driven applications because each operation is seamlessly instrumented.

To handle an event, one simple can pick from the events sent and write a job to process the event data in a background job.

The plugin should:

* have conventions to name the events
* be highly customizable
* allow the develop to determine what types of operations to send
* allow/deny based on a set of rules
* redact sensitive information

## Info

* https://www.inngest.com

The issue names no repository files, tests, or entry points. Start by locating the existing plugin system and GraphQL execution hooks, then review how plugins configure event handling and data filtering. Done means a documented Inngest integration with event naming, operation selection, allow/deny rules, and sensitive-data redaction.

Written by the indexing model from the issue text.