Cache pagination: add FieldNameGenerator and EmbeddedFieldsProvider

[BoD]

In this PR, 2 APIs are added:

• FieldNameGenerator to control how field names in records are computed. The default implementation uses CompiledField.nameWithArguments, and a Relay aware ConnectionFieldNameGenerator version is also provided. This unlocks cases where the pagination arguments are inside an input type. This is a reprise of this previous PR.
• EmbeddedFieldProvider to control which fields should be embedded in a record. The default implementation uses CompiledNamedType.embeddedFields, and a Relay aware ConnectionEmbeddedFieldsProvider version is also provided.

Also, a CompilerArgumentDefinition is introduced, to more cleanly separate an argument value vs its definition (and sorry this makes this PR big with the .expected - I can separate this to another PR if preferred!). (this will go in a separate PR)

With this, the Pagination mechanism is usable without any directives in extra.graphqls (#5666), an example is given in ConnectionProgrammaticPaginationTest.

[netlify]

✅ Deploy Preview for apollo-android-docs canceled.

Name	Link
🔨 Latest commit	79ad292
🔍 Latest deploy log	https://app.netlify.com/sites/apollo-android-docs/deploys/660d907bedce2f0008d95eba

[martinbonnin]

Can we keep getName and isKeyas deprecated?

[martinbonnin]

What about generating the definitions only once and referencing them here?

First:

// type
class Query {
  // field
  class Reviews {
    companion object {
      // argument
      val episode = CompiledArgumentDefinition.Builder("episode")build()
      val starsFloat = CompiledArgumentDefinition.Builder("starsFloat").build()
    }
  }
  companion object {
    val type: ObjectType = ObjectType.Builder(name = "Query").build()
  }
}

Then

 CompiledArgument.Builder(Query.Reviews.episode).value("JEDI").build()

[martinbonnin]

We could make this even more typesafe and also save a few string comparisons

interface CompiledFieldDefinition

// type
class Query {
  // field
  class Reviews {
    companion object {
      // argument
      val episode = CompiledArgumentDefinition.Builder("episode").build()
      val starsFloat = CompiledArgumentDefinition.Builder("starsFloat").build()
      
      val __definition = object: CompiledFieldDefinition {} 
    }
  }
  companion object {
    val type: ObjectType = ObjectType.Builder(name = "Query").build()
  }
}

And then

interface EmbeddedFieldsProvider {
  fun getEmbeddedFields(context: EmbeddedFieldsContext): List<CompiledFieldDefinition>

Not sure if it's worth it though...