Add filters in notifications endpoint

[rodolfomiranda]

This PR address issue #266 . It adds to NotificationCollectionEnd three optional query parameters

• read to filter by the read property of the note (true or false).
• route to filter by the route r property in the attributes section (a) if exists.
• order to order the results by datetime in asc or desc order.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.11%. Comparing base (18d3ad7) to head (50543d8).
Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #267      +/-   ##
==========================================
+ Coverage   93.06%   93.11%   +0.04%     
==========================================
  Files          36       36              
  Lines        7121     7243     +122     
==========================================
+ Hits         6627     6744     +117     
- Misses        494      499       +5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[lenkan]

Very helpful feature!

Question: I am not familiar with the notifier implementation, but this looks like it would load all notes in to memory, then filter them? Would it make sense to instead implement the filtering in keripy, utilizing the iterator to avoid loading all notes into memory?

[rodolfomiranda]

That's a good point. The optimal way is to implement it in keripy but it needs to run the iterator also on the countAll function. However, for the order part we still need to get them all in memory before pagination.
I can move it there easily, but I need the feedback from others specially @pfeairheller. If we are in agreement, I'll adapt this one and create a onother in keripy.

[rodolfomiranda]

I created a PR in KERIPY (WebOfTrust/keripy#816) that should be a more efficient way to implement the ordering and filtering.
I'll put this PR in draft until the keripy PR is being review. If it's merged, I'll adapt this one.

[pfeairheller]

I've commented and requested changes in (WebOfTrust/keripy#816). We can readdress this issue when that is resolved.