Fixes#420
I have no idea why `DocumentsContract.getTreeDocumentId` don't work. The docs of this method is quiet useless especially because of the typo: "Extract the via Document#COLUMN_DOCUMENT_ID from the given URI". The method returns only the path segment directly after the `tree` section which means the root of the selected location.
The good thing is that it is 100% reproducible and gets fixed by using `DocumentsContract.getDocumentId`. The problem exists since version 1.5.4. What I don't understand is why it worked in 1.5.3 because there the `DocumentsContract.getTreeDocumentId` returns the same garbage, I would understand the problem if it would exists since version 1.5.0 but 1.5.4 is weird. Crazy too is that this happens only with (crypto) folders and not (crypto) files.
"Vault not found" dialog is displayed during unlocking if it contains a blank character due to encoding twice. MicrosoftGraph now encodes the provided path to `itemWithPath` itself.
Fixes#419
For example, if authentication recovery fails, we load the vault from the database, which may result in a vault format -1 before this commit. We try to avoid this by overwriting the state after the authentication succeeds again, but we can't always avoid the vault format being -1 if, for example, during authentication the user changes activity, so we now store these fields in the database and update them if they have changed during unlock to prevent these states. Alternatively we could have locked the vault but from a UX point of view it makes no sense that the user has to unlock the vault again just because e.g. the token has to be refreshed.
If e.g. a cloud gets updated during token refresh while browsing files we authenticate, save the updated cloud, update the vault and now no longer lock other vaults from the same cloud but update them too.
CloudList gets refreshed and token is updated, if the token update is faster, resuming overwrites the delegates in DispatchingCloudContentRepository again due to authentication fail because the old folder is used in the onFolderReloadContent because folder in BrowseFilesActivity isn't yet updated.
Write external storage got removed due to forced scoped storage. Local storage cloud is now only available using the storage access framework implementation. Migration still needs to be implemented as well as how to recover when the authentications fails in the LocalStorageAuthStrategy.
Fixes#251
New vaults should be created using HS256 to be compatible with the desktop and iOS app. Before, we was defaulting to HS512. Now we specify the correct version.
While unlock, the algorithm specified in the header is used.
Fixes#366
