Support qvitter api notifications

@kaniini @lambadalambda @eal

After short researching i found out that:

Qvitter API endpoint doesn't give you the original post contents for favorites/repeats. This means either fetching each post individually (slow and bad), or searching for post client-side (which means missing favs again). Meanwhile mastoapi does have original post (except for mentions).

Proposed solutions:

Using QvitterAPI as is

• • compatibility with other BEs
• • missing notifications (favorites only, i think) OR http request for each notification

Extending QvitterAPI to have original post contents

• • theoretically we can add everything, not just html of post but, for example entire post the mention is replying to so we can always show reply-to tooltip even if it's not present in allStatuses
• • relying on extension would probably mean either falling back to current way of notifications in pleroma-fe or to searching for post in allStatuses because otherwise we would break notifications alltogether for other BEs.
• • have to make changes to Pleroma-BE as well.

Using MastoAPI

• • least work
• • mixing APIs in FE (i still don't see much wrong with it if we are gonna switch APIs in the future anyway)
• • no is_seen field
• • API isn't in our control and maybe could change at some point, we can hope that new api will be /v2/ and not changing the /v1/

Making our own API for notifications

pretty much same as extending QvitterAPI

https://shigusegubu.club/notice/4402332 thread discussing it with @eal

for now i'll try using QvitterAPI and searching for post in allStatuses.

even if it makes me cry

mentioned in merge request !306 (merged)

closed via merge request !306 (merged)

mentioned in commit 673f0fca