Sequential call to remote schema with multiple root on Query

I have currently upgraded to v2 and now a query with mutiple roots are getting send each separatelly and sequencial to my remote schema.

Example query:

```gql
query {
users(limit: 1) {
id
}

retailers(limit: 1) {
id
}
}
```

Before v2, my remote schema received one connection with the query, now with v2 the server receive 2 connections with a single query like:

First connection:

```gql
query {
users(limit: 1) {
id
}
}
```

Second connection:

```gql
query {
retailers(limit: 1) {
id
}
}
```

Is there any way to prevent that?

No source file, test, or entry point is identified in the issue. Start by reproducing the v2 query against a remote schema and compare the requests with the pre-v2 behavior. Done means determining whether multiple root fields can be sent in one request, or documenting the supported behavior and its limitation.

Written by the indexing model from the issue text.