Delegate parsing of CQL to pygeofilter in a more unified way

[ricardogsilva]

The current parsing of CQL follows different code paths depending on the request, for example:

• for GET requests, we use the pygeofilter ecql parser
• for POST requests, in the postgresql provider we use pygeofilter's cql_json parser
• for POST requests, in the elastic provider we use a custom parsing strategy that involves pydantic and other logic

Given that pygeofilter now has support for elastic as a backend and also supports both ecql and cql_json we can try to unify the CQL parsing and possibly even remove the pydantic and custom logic bits. We'd rely on pygeofilter for filtering CQL in a more unified way.

[github-actions]

This Issue has been inactive for 90 days. As per RFC4, in order to manage maintenance burden, it will be automatically closed in 7 days.

[github-actions]

As per RFC4, this Issue has been closed due to there being no activity for more than 90 days.