What Android version introduced 'Credential Manager' as the unified API for passkeys, passwords, and federated sign-in, and what security improvement does it provide over the legacy Smart Lock/Autofill API?

• A.Android 13 introduced Credential Manager to replace AccountManager; it keeps each credential in a Google Drive backup wrapped with the lock-screen PIN, and apps read them back through a foreground service rather than a system-drawn sheet
• B.Android 12 introduced Credential Manager to extend the Keystore API and park passwords in StrongBox; the improvement over Autofill is that a credential stays inside the requesting app's own process, the selection sheet is drawn there too, and the framework supplies the icon set with the accessibility labels
• C.Android 14 introduced the Credential Manager API; it provides a unified bottom sheet for passkey, password, and federated identity selection, and passkeys created through it are hardware-backed by the device's TEE/Secure Enclave - eliminating phishable passwords for supporting apps