Check capabilities of remote server in federated conversations

[Antreesy]

ATM only 29-29 can be federated, but we need to check in future if new features are supported by both servers

• [x] Storing / reading:
  • [x] federationsStore -> capabilities -> per token
• [x] Using:
  • [x] useCapabilities wrapper to check room and decide: -> local capabilities or remote

[nickvergessen]

This is done @Antreesy ?

[Antreesy]

Now we're only limiting functionality at federated conversations, based on our local 'federation-v1'. Need to add some things for:

• getting remote server capabilities and keep them per conversation / per remoteServer
• adding a wrapper for @nextcloud/capabilities, and use relevant sources for local and federated rooms

[Antreesy]

Keep it open, until wrapper is backported. Need to check again later (when it comes back to some major feature updates in main), so we could test this wrapper server-to-server and check that it behaves as expected