feat: cache aggregates by owner results until they are updated

[Psycojoker]

Optimize aggregates API route using caching

Related Clickup or Jira tickets : ALEPH-363

Self proofreading checklist

• Is my code clear enough and well documented
• Are my files well typed
• New translations have been added or updated if new strings have been introduced in the frontend
• Database migrations file are included
• Are there enough tests
• Documentation has been included (for new feature)

Changes

Introduce a small in memory cache based on defaultdict because aiocache requires async and most db related methods aren't async so we can't use it.

We cache on get_aggregates_by_owner call and invalidate the cache on PostgreSQL after_update and after_delete events to ensure we don't miss any update/delete.

How to test

Running the tests should be enough, otherwise you just hit the aggregates API endpoint several time to raise the cache and wait for an aggregate to be updated to see if it works.

[Psycojoker]

Right now this is using ORM events, it should be good but I'm not 100 sure, maybe we need to switch to PostgreSQL event triggers instead to ensure that event if another process works on an aggregate the cache will be invalidated?