Fix web locks API leadership guard logic

[findolor]

Chained PR

• Update fetch vaults query performance #2313

Motivation

In our implementation whenever we opened up a new tab, instead of returning a non-value or an error value for an unavailable lock, it was holding onto it making the tab stuck in the acquiring process. This PR aims to fix that by failing fast and making sure the type can exit out of the sync process.

Solution

• Use the correct parameters when calling requests

Checks

By submitting this for review, I'm confirming I've done the following:

• made this PR as small as possible
• unit-tested any new functionality
• linked any relevant issues or PRs
• included screenshots (if this involves a front-end change)

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch local-db-web-lock-api

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}