* Provide cross platform compatible versions of createFile() and createNewVersion()
The exist implementations are deprecated as they only work in a browser and support a different type of contents from MatrixClient.uploadContent()
* Fix MSC3089 content upload meta data in NodeJS runtime
* Break unstable createFile() and createNewVersion() instead of deprecating
Test using NodeJS types instead of mocked browser Blob
* chore: remove incorrect comment
The diff isn't super clear on how this works, but the general idea is that the MSC3089Branches (files) now know which directory they came from, and the directories (MSC3089TreeSpace) can tell when files are triggering uploads referencing themselves so it can add all the replacement metadata onto the event.
There's a few challenges with how relations work in the js-sdk which has shaped the API surface exposed by this change. Specifically, there is a `getVersionHistory()` function instead of a function to get a certain prior version: the js-sdk doesn't track parent events in the relation structures so cannot determine what the event could have replaced.
In order to trigger the built-in relations structures, we must trigger decryption with `emit: true`. This is so an internal listener in the relations system can pick up `Event.decrypted`.
