feat: how should we manage app user configuration defaults

[awentzel]

In the event that a user does not have a mobile device with biometric sensors, they have other preferred methods of multi-factor authentication, or they want extra layers of security and fallback methods with which to authenticate, we need to come up with a list of other services or capabilities in order to provide user choice in applications that implement this package.

What level of app user configuration should be supported to opt-in to MFA?

• 1F: Username/Password option available through API (not an option with Otio as requires 2FA w/Veroway)
• 2FA: Username/Password option with text or email verification
• MFA: Username/password option with MFA using biometrics

Ideally, iVault includes API to support all of these opt-in options for users and/or based on application configuration with graceful fallback if necessary.

### iValt Tasks
- [ ] Work with iValt on existing capability.
- [ ] Work with iValt on any new capability.
- [ ] Work with iValt to improve existing product documentation and / or engineering docs.
- [ ] Associate this work item or tasks with iValt issues if approved by iValt on roadmap.

### TAS Tasks
- [ ] Update documentation around each of the above task
- [ ] Create example scenarios for each option
- [ ] Create wrapper capability for each scenario

[awentzel]

@KingOfTac please update to include any other tasks related to this issue including an steps to replicate the problem or constraints you mentioned.