Update SDK to latest specs

[AndreasGassmann]

Over the last few months, there were a couple of improvements and changes made to the specs and the typescript SDK. This is not an extensive list, but some of the things we have to investigate:

• [x] matrix.papers.tech is being phased out, instead beacon-node-1.sky.papers.tech should be used

• [x] To support older homeserver versions, the "createRoom" endpoint has to specify the room_version, which needs to be hardcoded to "5". If this is not specified, it will always use the latest version and can result in problems when talking to users on old homeservers.

• [x] Multi-node support was added to the typescript SDK. The second node is beacon-node-0.papers.tech:8448

• [x] One of the big issues with multi-nodes in the typescript SDK was to keep a consistent state. If the SDK caches the currently active room per peer, it's important that the room is updated every time a message is received or a new invite is received. The peer information also has to be updated, either when a new peer is added, a message is received, or an invite is received and joined. That way, messages are always sent to the correct room and the correct user is addressed.

• [ ] 2.3.0 (unreleased) introduces "encrypt/decrypt" requests

• [ ] 2.3.0 (unreleased) will most likely switch to public_chats instead of trusted_private_chats. This will allow peers to re-join if they lose connection and log in on another homeserver. More info will follow once this is specified and tested.

[jsamol]

The multi-node support will be included in the upcoming v2.0.0 release.