bug: query plan fails resolve dependencies

[laststylebender14]

for example for following schema, user field is dependent on the userId field.

schema
  @server(port: 8000)
  @upstream(baseURL: "http://jsonplaceholder.typicode.com", httpCache: 42, batch: {delay: 100}) {
  query: Query
}

type Query {
  posts: [Post] @http(path: "/posts")
}

type User {
  id: Int!
  name: String!
}

type Post {
  id: Int!
  title: String!
  userId: Int @http(path: "/users/1", select: "{{.id}}")
  user: User @http(path: "/users", query: [{key: "id", value: "{{.value.userId}}"}], batchKey: ["id"])
}

logs:

 INFO File read: ./examples/jsonplaceholder.graphql ... ok
 INFO N + 1 detected: 1
 INFO 🚀 Tailcall launched at [127.0.0.1:8000] over HTTP/1.1
 INFO 🌍 Playground: https://tailcall.run/playground/?u=http://127.0.0.1:8000/graphql&utm_source=tailcall-debug&utm_medium=server
 INFO GET http://jsonplaceholder.typicode.com/posts HTTP/1.1
 INFO GET http://jsonplaceholder.typicode.com/users/1 HTTP/1.1
 INFO GET http://jsonplaceholder.typicode.com/users?id HTTP/1.1

Query Plan should be able to figure out which operations are dependent and which are independent. Independent operations can be executed in parallel manner.

[tusharmath]

Let's throw a validation error for now.