fix: handle expired Redis lock release gracefully

[rafel-roboflow]

Resolves dg-319

When a redis lock's TTL expires before the code inside the lock finishes executing, calling release() throws "cannot release a lock that's no longer owned".

What does this PR do?

we want to avoid showing this error in the frontend.

Related Issue(s):

Type of Change

• Bug fix (non-breaking change that fixes an issue)

Testing

• I have tested this change locally

Test details:

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code where necessary, particularly in hard-to-understand areas
• My changes generate no new warnings or errors
• I have updated the documentation accordingly (if applicable)

Additional Context

---

Note

Low Risk
Small, localized change to lock cleanup behavior; main risk is potentially masking unexpected premature lock expiry (now surfaced only via a warning log).

Overview
BaseCache.lock now catches redis.exceptions.LockNotOwnedError when releasing a lock and logs a warning instead of raising, preventing failures/noisy errors when the lock TTL expires before the protected work completes.

^{Written by Cursor Bugbot for commit 1557dad. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}