Description

The identity verification screens are always in English, whatever language the app is set to. They come from Didit's hosted UI, not from our code, so the translations added in #1145 do not reach them.

Didit's create-session API takes a language parameter (ISO 639-1) that controls the verification UI. Both ru and uk are supported, with the same codes the app already uses. We currently omit it, and Didit's fallback — detecting the browser language — does not work inside the Tauri webview.

Two flows create a Didit session and both are affected:

• KYC verification, VerificationController in evault-core
• Account recovery, RecoveryController in evault-core

Recovery is the one that matters most: someone recovering an account is already in trouble, and an English-only screen at that moment is the worst place for it.

Steps to reproduce

1. Set the device language to Russian and launch the wallet. The app is in Russian.
2. Start identity verification from the ePassport screen.
3. The Didit screens ("Choose your verification document", "Take photo of the front side") are in English.

Expected behavior

The verification screens follow the language the app is running in.

Supporting Media

Reported by QA on a Russian device. The surrounding native chrome shows "Отмена" while the content stays English.

Additional Context

The wallet posts an empty body to POST /verification/v2; evault-core then posts { workflow_id, vendor_data } to Didit's /v3/session/. The locale has to travel from the wallet through the provisioner to Didit, so this spans both.

Docs: https://docs.didit.me/sessions-api/create-session