Fix hydration selection set on nested input objects

[gnawf]

Refer to the test/src/test/kotlin/graphql/nadel/tests/next/fixtures/hydration/HydrationNestedObjectInputTest.kt test.

Effectively when the user sets up a hydration

type Issue {
  assigneeFilter: IssueUserSearchInput
  assignee: User
    @hydrated(
      field: "userByFilter"
      arguments: [{name: "filter", value: "$source.assigneeFilter"}]
    )
}
type IssueUserSearchInput {
  filter: [IssueUserSearchFilterInput!]
}
type IssueUserSearchFilterInput {
  parentId: String
  subEntityTypes: [String!]
}

and

type Query {
  userByFilter(filter: UserSearchInput!): User
}
input UserSearchInput {
  filter: [UserSearchFilterInput!]
}
input UserSearchFilterInput {
  parentId: String
  subEntityTypes: [String!]
}
type User {
  id: ID!
  name: String
}

We need to ensure the selection set is

assigneeFilter {
  filter {
    parentId
    subEntityTypes
  }
}

whereas it's currently

assigneeFilter {
  filter
}

as we don't handle nested selection sets.

Also refactored it to create the ENFs ahead of time during validation.

[github-actions]

Test Results

  614 files  +  614    614 suites  +614   1m 6s ⏱️ + 1m 6s
2 030 tests +2 030  1 508 ✅ +1 508  522 💤 +522  0 ❌ ±0 
2 038 runs  +2 038  1 516 ✅ +1 516  522 💤 +522  0 ❌ ±0 

Results for commit 2cb6fff. ± Comparison against base commit 6f26e6b.

♻️ This comment has been updated with latest results.

[gnawf]

New code here, the ENFs are built during validation time, now we just insert them from the instruction.

[gnawf]

Added missing copy.

[gnawf]

The way these fields are generated was changed, now it's merged together which should be better.

Should execute the same way since fields would be merged at execution time.

[gnawf]

Test have new source fields code on by default.

[gnawf]

We now build the entire ExecutableNormalizedField ahead of time instead of just computing the required NadelQueryPath

[gnawf]

For FFing

[gnawf]

This is the main change, before this was

nadel/lib/src/main/java/graphql/nadel/validation/hydration/NadelHydrationSourceFieldValidation.kt

Lines 89 to 93 in 2cb6fff

	return hydrationSourceType.fields
	.map { field ->
	hydrationValueSource.queryPathToField.plus(field.name)
	}
	.asInterimSuccess()

Which only selected one level of children.

Now it iterates through the required input object fields and then creates the selection set from that. It does this recursively to create the correct selection set.