feat: handle primary SRP switch cases

[mathieuartu]

Explanation

We discovered that users leverage the "forgot password" flow to switch their primary SRPs in clients.
This is breaking auth & user storage, and this PR fixes that so that our controller can handle use cases where the primary SRP changes to another one.

Additional changes in clients should be made:

• Signing out the user when submitting the forgot password form on extension

Please note that no changes in this PR introduces breaking changes.

References

Related to: https://consensyssoftware.atlassian.net/browse/IDENTITY-60

Changelog

@metamask/profile-sync-controller

• REMOVED: AuthenticationController doesn't use the _snapPublicKeyCache anymore.
• CHANGED: UserStorageController storageKeyCache can now hold multiple values.
• CHANGED: SDK getStorageKey now takes a message argument for cache navigation purposes
• CHANGED: SDK setStorageKey now takes an additional message argument to leverage cache usages

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've highlighted breaking changes using the "BREAKING" category above as appropriate
• I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes