[Bug]: New version of an existing file cant be uploaded while the file is locked

⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

When a file is locked and you have to upload a new version of the same file, you´ve to unlock it and upload the new version when before the user who blocked it could overwrite it while being blocked

Steps to reproduce

1. A file exists
2. File is locked while editing
3. Upload the file again edited
4. Failed to upload the new version of the file

Expected behavior

The file should be overwritten by the user who blocked it when a new version is uploaded

Installation method

Manual installation

Operating system

RHEL/CentOS

PHP engine version

PHP 7.4

Web server

Apache (supported)

Database engine version

MariaDB

Is this bug present after an update or on a fresh install?

Fresh Nextcloud Server install

Are you using the Nextcloud Server Encryption module?

No response

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

No response

List of activated Apps

--

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response

No source files, tests, logs, or entry points are named. Start by reproducing the locked-file upload flow described in steps 1–4, then trace the files_lock handling for uploads by the user who holds the lock. Done means that user can upload a new version without unlocking it, with regression coverage for the reported steps.