Embed GraphQL metadata in the jar/klib

[martinbonnin]

Use case

As of today, we use a separate file to store GraphQL metadata used by the apollo compiler. This means in multi-module scenarios, one typically has to do something like so:

dependencies {
  implementation(project(":schema"))
}

apollo {
  service("service") {
    dependsOn(project(":schema"))
  }
}

While working, this setup is a bit cumbersome and error prone. It's possible to forget one of the two dependencies.

Instead, we could embed the required GraphQL information in the .jar/.klib file so that the apollo compiler doesn't have to pull an additional artifact.

Describe the solution you'd like

No response