[Spike] Investigate the need for using the KeyguardManager separately

[jonalmeida]

Description

In the BiometricPromptPreferenceFragment and in some places in BaseBrowserFragment, we try to fallback to the KeyguardManager for PIN/password support.

This isn't something that should be needed since we allow PIN/password as a fallback when we make a request through the Biometric support library. The biometric library also abstracts out the correct calls for backward compatibility for devices that do not have support for full support.

Something we could adjust is the code checking for biometric support for DEVICE_CREDENTIAL.

Deliverables

• Can we remove the complexities of the KeyguardManager from our code base and use the AndroidX library alone? The less code, the better. :)
• If we do need it, can we hide those within the BiometricPromptFeature so that it can be used in multiple places since we have two separate impls of a similar code flow?

┆Issue is synchronized with this Jira Task

[stale]

See: #17373 This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[jonalmeida]

I came across this issue again when reviewing the backport of BiometricPromptFeature here: mozilla-mobile/android-components#12291

I see that we are using the KeyguardManager in components as well for feature-autofill authentication and I'm still unsure why we need both.

[stale]

See: #17373 This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[boek]

Moved to bugzilla: https://bugzilla.mozilla.org/show_bug.cgi?id=1814143

Change performed by the Move to Bugzilla add-on.