Flask-rest-jsonapi-next

- fix: wrong import from dateutil

- fix: allow top level filters to be JSON objects

Previously filters had to be arrays:


/books?filter=[{"name": "title", "op": "eq", "val": "foo"}]


Now following works too:


/books?filter={"name": "title", "op": "eq", "val": "foo"}


- fix: initial filter value coercion implementation from `0.42.0` was incorrect

- fix: coerce filter values to Python objects
Combination of SQLAlchemy 2.x and psycopg 3.x no longer accepts query parameters as
strings for ie. integers and date-times. Query like following:

py
User.query.filter(User.id == "42").first()


results with

log
ProgrammingError: (psycopg.errors.UndefinedFunction) operator does not exist: bigint = character varying


Ideally, this would've been resolved in either of these libraries or in applications
themselves. And in most cases this the only solution. But in `flask-rest-jsonapi-next`
we can workaround most of these errors by trying to coerce filter values into correct
types.

- fix: don't log stacktrace for common exceptions
- fix: defend from empty filters

- removed restriction on SQLAlchemy version, library now works with SQLAlchemy 2.x
- working with SQLAlchemy 2.x layer requires some changes in client code, otherwise
there might be performance penalties
- added docs section on SQLAlchemy 2.x usage
- tested with psycopg 3

- fix: missing import