Actually implement what the comment says: we want to cap the progress at
99% so we wait for the request to complete with 200 before going to
100%.

squash: Change the way we pass the list of files from the backend.

squash: Remove actions to sync local state with remote.

* While making the file size limit configurable, we managed to have files dragged and dropped over the whole conference window.

Rework sync so uploading multiple files at once or several moderators
uploading files simultaneously doesn't break synchronization.

The current room metadata plugin operates on <key,value> pairs and we
were using a generic "files" key and using a nested object as our value.
Since with every operation the entire object is replaced it's easy to
get out of sync because one needs to be sure to have the full state
before overwriting it.

This is not realistic.

We'll look into making the metadata plugin more flexible in order to
support add / delete operations also on nested objects, but for the time
being the following will suffice:

Use a key prefix, so each file has en entry in the room metadata, like
so: "files.<the file ID> -> file metadata". This means that when a file
is deleted we just empty the metadata. The metadata plugin doesn't
currently support removing existing keys.

* feat(file-sharing): added shared file/files author display name

Stay at 99% completion while we wait for the final reply to the request.

Co-authored-by: Saúl Ibarra Corretgé <saghul@jitsi.org>
Co-authored-by: Lucian-Paul Torje <lucian-paul.torje@8x8.com>