fix: Only update lock timeout when it is not infinite

[juliusknorr]

Otherwise if the desktop client tries to refresh an infinite lock it will auto expire on the next check as it will be set to 1 second (0 - (-1) - 0)

[max-nextcloud]

nice catch!

[Jerome-Herbinet]

Hi @juliushaertl,
Can you describe a buggy behavior which will be fixed by your PR and how (in order, for me, to understand well) ?
Thanks

[juliusknorr]

When using open locally the desktop client will lock the file and send another lock request to extend once it is opened. This lead to the lock disappearing almost immediately after opening locally.

[juliusknorr]

/backport to stable29

[juliusknorr]

/backport to stable28

[backportbot]

The backport to stable29 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable29
git pull origin stable29

# Create the new backport branch
git checkout -b backport/288/stable29

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick c5ec9cbe

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/288/stable29

Error: Failed to clone repository: Failed to checkout branches: error: pathspec 'stable29' did not match any file(s) known to git

---

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

[juliusknorr]

/backport to stable27

[Jerome-Herbinet]

When using open locally the desktop client will lock the file and send another lock request to extend once it is opened. This lead to the lock disappearing almost immediately after opening locally.

OK thanks