fix: [OCISDEV-1435] resolve vault permanent links opened outside the vault

[gauravsoni119]

A permanent link copied inside the Safe is <server>/f/<fileId> without /vault, so it opens in a normal Drive tab. The redirect added in #12881 detects vault files by comparing against the vault_storage_provider capability, but that value was only sent on capabilities?vault=true. A Drive tab got "", the redirect never fired, and the user saw "An error occurred while resolving the private link".

Fix is in reva: the provider id is now part of every capabilities response when vault mode is enabled. This also fixes vault notifications showing in the Drive view and the invite form not recognizing vault resources. No frontend change needed. The vendor change mirrors the reva PR.

Tests: new reva unit tests; new acceptance scenario in apiVault/vault.feature checking the plain capabilities endpoint returns the id (needs vault CI). Verified manually on a local ocis_full vault deployment.

• reva: fix(ocs): [OCISDEV-1435] announce vault storage provider on every capabilities response reva#747
• builds on fix: [ocisdev-1199] resolve vault permalinks into vault scope #12881
• Jira: OCISDEV-1435

[kw-security]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[gauravsoni119]

Will do in another PR in reva.