A generic liveness camera-access error should be diagnosed using the nested SDK error

A generic liveness camera-access error should be diagnosed using the nested SDK error and browser container before advising permission changes. A successful server-side liveness-session creation does not prove that the client can start the camera. In an embedded browser, an SDK message that getUserMedia is not implemented supports trying the same link in a supported standalone browser; it does not prove that the user denied permission, that the physical camera is broken, or that every version of the embedding app is incompatible. Capability booleans alone are weaker than the actual camera-start result. Recovery remains unverified until a later capture succeeds.