BUG - Server Side Filter - Fix types and use context in resolveAggregations

[joneubank]

arrangerServer takes a custom getServerSideFilter property so that each request can have filters applied based on server logic. The current type for GetServerSideFilterFn does not include the GQLRequestContext in its function arguments, which is provided the function by both buildSets, and resolveHits. We also need to update resolveAggregations to provide the context to the serverside filter.

[joneubank]

In addition to the two changes listed above, the GQL Context object does not include access to any of the incoming request information by default. There is a property for the arragnerServer graphqlOptions.context that can be provided a function that has access to the req, res, and connection details and return properties to add to the context option. This seems to be quite convoluted though. It would be simpler for the context object to always contain the request object. If we add the request details by default then we would skip needing to also detail context information in the arrangerServer definition. One reason to keep this up front graphqlOptions.context function is so that we can do the auth check a single time (for example to not repeat it for both aggregations and hits). This way, auth information could be placed into context instead of just the incoming request info.