[Bug]: File locks UI doesn't allow unocking for owner

⚠️ 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 OR Nextcloud Community Forum (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

The Files Lock feature allows users to manually lock files to prevent concurrent modifications. The file owner is always allowed to unlock any existing lock on an API level, regardless of who created the lock, but the frontend UI only enables the Unlock action when the current user is the lock owner.

Steps to reproduce

Alice shares the file with Bob with edit permissions.
Bob locks the file.
Alice can't unlock the file from her side via the UI, even as the file owner.

Expected behavior

Alice can unlock the file any time as the owner

Nextcloud Server version

32

Operating system

Debian/Ubuntu

PHP engine version

PHP 8.3

Web server

None

Database engine version

None

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

None

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

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

Configuration report

List of activated Apps

Nextcloud Signing status

Nextcloud Logs

Additional info

No response

Start by tracing the Files Lock frontend action and compare its owner check with the existing API behavior described in the issue. Reproduce the Alice-and-Bob scenario, then verify that the file owner can unlock Bob's lock through the UI without removing the restriction for other users.