[keyring-controller] Mitigate run conditions with >^16.x

[mikesposito]

After merging these changes (Likely released in @metamask/keyring-controller version 16.0.0 at the time of writing):

• [keyring-controller] Avoid calling mutable public functions internally core#4181
• [keyring-controller] Lock controller mutex on write operations core#4182
• [keyring-controller] Remove #getMemState returns core#4199
• [keyring-controller] Atomic Operations core#4192
• [keyring-controller] Add withKeyring method core#4197

@metamask/keyring-controller should be updated to a minimum version of (at the time of writing) ^16.0.0 to bring the changes to the client.

Update guide

The version 16.0.0 (presumably) brings many improvements, especially in terms of run conditions mitigation. There are two main breaking changes between 15.x and 16.x:

• KeyringController's methods don't return the entire controller state anymore: in case that's still needed, clients can use the controller.state getter
• persistAllKeyrings (and relative :persistAllKeyrings action) has been deprecated, and an alternative for methods that were deprecated in previous versions has been provided now: the withKeyring method
  • Clients (and other controllers) can leverage the withKeyring method to drop usage of getKeyringsByType, getKeyringForAccount, and persistAllKeyrings, by passing a keyring selector and a callback that will be executed as a mutually exclusive controller operation