Wire up device auth key to autofill service [PM-26177] (8/8)

[iinuwa]

🎟️ Tracking

PM-26177

📔 Objective

This updates the AutofillCredentialService to try to fulfill incoming requests using the device auth key before unlocking the vault and trying passkeys from there.

The DeviceAuthKey service is responsible for checking the record identifier to make sure that it only answers a request if the cipher ID matches.

Depends on #2297.

⏰ Reminders before review

• Contributor guidelines followed
• All formatters and local linters executed and passed
• Written new unit and / or integration tests where applicable
• Protected functional changes with optionality (feature flags)
• Used internationalization (i18n) for all UI strings
• CI builds passed
• Communicated to DevOps any deployment requirements
• Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 Reviewer guidelines

• 👍 (:+1:) or similar for great changes
• 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
• ❓ (:question:) for questions
• 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
• 🎨 (:art:) for suggestions / improvements
• ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
• 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
• ⛏ (:pick:) for minor or nitpick changes

[github-actions]

Checkmarx One – Scan Summary & Details – 26ef76b5-8d60-4703-b2ba-e2462354100e

Great job! No new security vulnerabilities introduced in this pull request