Handle lazy-resolved values from connection resolve functions

[rmosolgo]

Starting in 1.3.0, graphql-ruby says it will handle certain classes lazily. But this is still broken for connections, since the lazy value is wrapped with a connection (I think?).

I need to test this behavior and make sure it's uniform with the rest of the gem (ie, connections should Just Work ™️).

This issue was first described here: Shopify/graphql-batch#26