redesigned Video Verification flow (remove password)

Currently, video verification requires you to set a password and then give it to the share recipient in a video call.

We could remove this by just having an 'approve' button. The main downside is that this would need to be supported in the mobile and web UI as a special thing when a video verification call takes place on the receiving side, and some logic on the accessing side too ofc, esp to store the 'approved' in a cookie.

Flow:

share link has:

• password
• Video Verification
• expiration date

When enabled, recipient gets a "request access" button only when visiting the share link. That button does the same as now - start a call.
The sharer gets the call and has a 'approve access' button. Once they have verified the identity of the recipient they click the button and access is granted.

other thoughts

• the approved access should be stored in a cookie on the system of the recipient?!?
• If so, the recipient should have a way of 'removing' this granted access, in case the data is super sensitive (maybe a 'logout'?) and somebody who steals their device could steal data...

Start by tracing the existing video verification flow in the mobile and web UI, including the current password exchange and access-side logic. Define the approval action, recipient cookie storage, and way to remove granted access; done means the described flow works across both interfaces.