tus: "file currently locked"

[infinite-persistence]

Sometimes, after the file has been uploaded (after the TUS stage), the notify call fails with "file currently locked". The backend is waiting for something (we are not sure what).

Usually, another notify should do that trick and in fact is being done, but the initially error wasn't caught, so we ended up with successful upload but with "file currently locked" shown.

Need to suppress the error message for this scenario (there might be other scenarios where this error message is correctly reflecting the situation).

[infinite-persistence]

Assessment above is incorrect.

• For super large files, the notify call will timeout after ~2 minutes.
• We do one more retry, but the "file is still locked", hence the popup.
• But at the backend, the SDK call will be done after the file is unlocked, so user eventually sees the claim confirming in the blockchain.

Not sure what's locking the file after the tus upload.

[infinite-persistence]

Requires https://github.com/OdyseeTeam/odysee-api/issues/401