Connection doesn't provide a request context for method based `getTotalCount`

Product

Hot Chocolate

Is your feature request related to a problem?

I have a very complex query system. We have over 300 entities in our "public" API and many more besides. When returning new Connection() from data fetching methods you can provide a getTotalCount async method. This is lovely but fails if you require anything to resolve from the service provider.

For myself since the API is very complex I have undertaken to duplicate the core logic of ConnectionType, EdgeType, ConnectionPageInfo (etc) in order to provide this and other functionality, but others may benefit from simply having access to the context for getTotalCount, thus allowing expensive count operations to only happen on demand instead of needing to pre-resolve everything from the service provider.

The solution you'd like

An overload should be provided with Func<HotChocolate.Resolvers.IResolverContext, CancellationToken, ValueTask<int>> getTotalCount

Start by locating the Connection implementation and how its method-based getTotalCount callback is invoked, then read the related ConnectionType, EdgeType, and ConnectionPageInfo types. Verify how IResolverContext is exposed to resolver callbacks. Done means the requested overload accepts the resolver context and cancellation token while preserving the existing callback form.