[PM-4081] Fix crash on export page

[aj-rosado]

Type of change

• Bug fix
• New feature development
• Tech debt (refactoring, code cleanup, dependency upgrades, etc)
• Build/deploy pipeline (DevOps)
• Other

Objective

Application is crashing to users that have biometrics active, updated to the most recent version without and try to export.
This is caused by a missing MasterKey, this fix creates the missing MasterKey if necessary at export.

Code changes

• UserVerificationService.cs: Calling method GetOrDeriveMasterKeyAsync to ensure that the MasterKey if doesn't exist is created. In case of success, use the same logic from MasterPasswordRepromptService to update the MasterKey and the UserKey
• CryptoService.cs: Created a method that updates the MasterKey and the UserKey based on the code from MasterPasswordRepromptService so that it can be reused by UserVerificationService
• MasterPasswordRepromptService: Replacing the code by the new created method from CryptoService

Before you submit

• Please check for formatting errors (dotnet format --verify-no-changes) (required)
• Please add unit tests where it makes sense to do so (encouraged but not required)
• If this change requires a documentation update - notify the documentation team
• If this change has particular deployment requirements - notify the DevOps team

[bitwarden-bot]

Checkmarx One – Scan Summary & Details – 7f6f0ca6-fa3c-45a0-877f-9d071c17f505

No New Or Fixed Issues Found

[andrebispo5]

LGMT 👍

[nextlevelgamesmn]

Type of change

• [] Bug fix
• New feature development
• Tech debt (refactoring, code cleanup, dependency upgrades, etc)
• Build/deploy pipeline (DevOps)
• [ X] Other

Objective

Application is crashing to users that have biometrics active, updated to the most recent version without and try to export. This is caused by a missing MasterKey, this fix creates the missing MasterKey if necessary at export.

Code changes

• UserVerificationService.cs: Calling method GetOrDeriveMasterKeyAsync to ensure that the MasterKey if doesn't exist is created. In case of success, use the same logic from MasterPasswordRepromptService to update the MasterKey and the UserKey
• CryptoService.cs: Created a method that updates the MasterKey and the UserKey based on the code from MasterPasswordRepromptService so that it can be reused by UserVerificationService
• MasterPasswordRepromptService: Replacing the code by the new created method from CryptoService

Before you submit

• Please check for formatting errors (dotnet format --verify-no-changes) (required)
• Please add unit tests where it makes sense to do so (encouraged but not required)
• If this change requires a documentation update - notify the documentation team
• If this change has particular deployment requirements - notify the DevOps team

Also having issue