Remove the Filter Extension dependency from Aggregation Extension requests

[jamesfisher-geo]

Related Issue(s):

• Remove dependency between Aggregate and Filter extensions  #715

Description:

• Removes the Filter Extension depenency from AggregationExtensionPostRequest and AggregationExtensionGetRequest. This can be done in the implementations.
• Improve the aggregations typing.

PR Checklist:

• pre-commit hooks pass locally
• Tests pass (run make test)
• Documentation has been updated to reflect changes, if applicable, and docs build successfully (run make docs)
• Changes are added to the CHANGELOG.

[vincentsarago]

I don't think the aggregate extension should depends on Search.

Users wil create the Search model using search_get_request_model by providing BaseSearchGetRequest and the list of extension they want to support

[jamesfisher-geo]

I don't think the aggregate extension should depends on Search.

Users wil create the Search model using search_get_request_model by providing BaseSearchGetRequest and the list of extension they want to support

Okay. Does the aggregation extension spec need to be updated to reflect this? The spec has the same fields as search with the addition of aggregations

[vincentsarago]

oh I see 🤦 that's my bad then.

it seems that the aggregate extension should depends on the search classes.

BUT the aggregate extension shouldn't influence the /search options