this test is currently failing. This is the result:

{
  dog {
    ... @defer {
      breed
      name
      owner {
        firstname
      }
    }
  }
}

I see 2 ways going forward:

• introduce a new class to represent a @defer block. This new class would share a type with ExecutableNormalizedField , so the children of an ENF could either be other ENFs, or @defer blocks.
• Build a map that associates fields with @defer outside of the ENF hierarchy, similarly to normalizedFieldToQueryDirectives.
  I'm leaning towards option 2 because it seems less intrusive

I created a version of createExecutableNormalizedOperation that takes Option

I feel like working with an instance of some object created on a per-execution basis would make accessing these values much easier. We could create instance fields instead of having to pass them down the stack.

Make this a Map

rename method to createDeferExecution

Use Map instead of Guava type

This should result in just 1 defer block

Not a blocker, but we should double-check what is the expected behaviour here with the drivers of the defer/stream spec change.
For reference, the Apollo server execution will block the response until breed is return in the initial payload, then it will sent a second, deferred, payload with breed again.

Based on the direction the working group is taking (graphql/defer-stream-wg#69) regarding de-duplication, I propose we keep only the non-deferred version of the field.
I can do it on a follow up PR.

Minor change: use maxLevel from options instead of passing it as argument