Remote schema N+1 issue with a Hasura Remote Schema

### Batch remote schema requests into one sql request

N+1 problem with a remote schema in a Hasura implementation. Specifically, a remote relationship is defined between a local table(employee) and a remote table (employeelanguages). The sample below causes multiple individual requests to the remote schema instead of a single batched request:
```

query Employee {
employee {
name
employeelanguages {
id
name
}
}
```

### Describe the solution you'd like

Make one SQL query to the employeelanguages instead of multiple queries.

### Describe alternatives you've considered

Start with the supplied Employee query and trace how Hasura generates requests for the remote relationship. Verify the current request count, then make the employee languages lookup use one batched SQL request; the query should return the same fields without individual remote requests per employee.

Written by the indexing model from the issue text.