For unknown error, there is now response body. So JSON.parse crash.
Updated TS types of patch-package.

…arge

Possible with last update of cozy-stack https://github.com/cozy/cozy-stack/pull/4069/files

Not totally agnostic. Linked to cozy-stack.

Will help next features link "share with".

When killing app during a backup, backup was stuck as running even if
it was not running. Now, if we start the app and backup is set as
running, we set it as to do because it is not possible. It is only
when app start, you we can still move between webview while a backup
is running

We try to stay as close as operating system :
- folder structure on Android
- album on iOS

On iOS, media are set with a remote path to '/' because there is no
folder in backup folder. But when restoring, remote path was set to
empty string so algorithm was considering these photos as not
backuped.

Backup folder is a magic folder. But in some part of the code, we
need to use the path of the backup folder from local backup config.
So now before uploading files, we check if the backup folder has been
renamed and we update local backup config if needed.

This reverts commit 2a1d096.

Like that, cozy-stack is able to cut the connexion before the end if
there is no space left on the device.

This is how I use it : `./gradlew allDeps > allDeps.txt`

We have an http2 issue when uploading a file to a cozy when we reach the
quota limit. In that case, the stack closes the connexion but it can
appears after having already send a few bytes. In that case, okhttp was
not returning the right headers and we ended up with a:
`stream closed: cancel`.

With this version, okhttp is returning the right header!

see the okhttp changelog:
https://github.com/square/okhttp/blob/master/CHANGELOG.md#version-500-alpha1
specially:
`Fix: Attempt to read the response body even if the server canceled the
request. This will cause some calls to return nice error codes like
 HTTP/1.1 429 Too Many Requests instead of transport errors like
SocketException: Connection reset and StreamResetException: stream was
reset: CANCEL.
`

Previous implementation would throw if the received error do not
contain any `errors` array. this can happen if the error is not thrown
by cozy-client

Also this commit improve type check to ensure the receive error is the
one we expect. Casting objects using `as` should be avoided as this
will never ensure type compatibility