[AlexAndBear]

Description

• Vaults in public links: the vault guard redirects to the unlock route without the context of the public link, so isPublicLinkContextRequired didn't recognize it and anonymous visitors were sent to the IdP login. For public links the guard now passes the route context along, so the unlock form opens in the link context and the vault opens after unlocking.

Before	After

Related Issue

• No issue, found in the functional bug sweep of the web client

How Has This Been Tested?

• test environment: local dev server, Playwright (Chromium)
• vault in a folder with a password protected edit link, opened logged out: unlock form instead of the IdP login, the vault opens after entering its password
• logged in: unlocking a vault works as before
• unit tests added

Types of changes

• Bugfix
• Enhancement (a change that doesn't break existing code or deployments)
• Breaking change (a modification that affects current functionality)
• Technical debt (addressing code that needs refactoring or improvements)
• Tests (adding or improving tests)
• Documentation (updates or additions to documentation)
• Maintenance (like dependency updates or tooling adjustments)