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 12 introduced Credential Manager as an extension of the Keystore API that stores passwords in StrongBox for hardware-backed protection
• B.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
• C.Android 13 introduced Credential Manager as a replacement for AccountManager; it encrypts stored credentials with the user's PIN and syncs them via Google Drive
• D.Android 11 introduced Credential Manager via Project Mainline as an APEX module update that adds FIDO2 support to the Smart Lock system