Provide additional parameters to support provision of execution context to Load and LoadAsync

Hi Aleksey

Statler here - you may remember me from such posts as

• https://github.com/DevExpress/DevExtreme.AspNet.Data/issues/367
• https://github.com/DevExpress/DevExtreme.AspNet.Data/issues/277

So, just when I thought I had every base covered, I have come across a new use case that I need to manage. I am hoping you can help me out here.

My case deals successfully with automapper projection by:

1. Registering CustomAccessors automatically from the automapper config (https://github.com/DevExpress/DevExtreme.AspNet.Data/issues/367)
2. Getting the IDs of all results from the Devexpress.AspNet.data expression compilation query
3. Querying the base type for all ids in (2), and using ProjectTo

This all works really well for ProjectTo(Mapconfig)

Where I have come unstuck is the overload of ProjectTo(Mapconfig, MapParameter) (https://docs.automapper.org/en/stable/Queryable-Extensions.html#parameterization)

This enables the injection of runtime variables into the projection and is a case I can't see a way to resolve as it is not possible to provide context in the CustomAccessors or CustomFilters. Would you be open to modifying the signatures for these methods to support the provision of context via an additional parameter to DataSourceLoader.LoadAsync / DataSourceLoader.Load

Start with the DataSourceLoader.Load and LoadAsync entry points and review the AutoMapper Queryable Extensions parameterization linked in the issue. Determine how an execution context should reach the projection while preserving the existing CustomAccessors and CustomFilters flow; done means both overloads support the requested runtime parameters.