fix(auth): Fix for when a General Security Exception is thrown due to tink error we will recreate the preference

[gpanshu]

• PR title and description conform to Pull Request guidelines.

Issue #, if available: #2548

Description of changes: This is a rare crash that can occur in the Google Tink + EncryptedSharedPreferences library. In order for Amplify to function properly, we rely on EncryptedSharedPreferences to securely hold data. This issue can be found in the Google IssueTracker here: https://issuetracker.google.com/issues/176215143

If the master key becomes unreadable or corrupt the only path forward is to delete and recreate the preferences. This is a destructive action.

How did you test these changes?
(Please add a line here how the changes were tested)

Documentation update required?

• No
• Yes (Please include a PR link for the documentation update)

General Checklist

• Added Unit Tests
• Added Integration Tests
• Security oriented best practices and standards are followed (e.g. using input sanitization, principle of least privilege, etc)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[mattcreaser]

Superseded by #2686