… `^21.0.4` (#32287)

<!--
Please submit this PR as a draft initially.
Do not mark it as "Ready for review" until the template has been
completely filled out, and PR status checks have passed at least once.
-->

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->
Bumping `@metamask/keyring-controller` to `^21.0.4`
```markdown

- Ensure no duplicate accounts are persisted ([#5710](MetaMask/core#5710))
```

[![Open in GitHub
Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/MetaMask/metamask-extension/pull/32287?quickstart=1)

Fixes: #32097

a duplicate account:
- Checkout on the v12.16.0 release branch and build locally (a version
with multi-srp support)
- Import or create an SRP (I used `child guilt hollow arrive average
popular nasty soon summer like scheme diary pill country rapid`)
- Import an account that is part of the mnemonic (e.g. I used
`0x80842b7e3cfb1118e86a427cdec418e3b4179ef5bbbfd71c02a76349831c8a8b`
which is the account at index 2 of the above SRP)
- Add a new account on the main HD - note that you'll be able to add the
account, but (1) the account is the same as the imported one
(expectable) and (2) the newly added account is wrongly labeled as
"imported"
- Lock the wallet
- Unlock it with the right password - you will see the reported error:
```
Error: KeyringController - The account you are trying to import is a duplicate
await in withLock
submitPassword	@	metamask-controller.js:4343
await in submitPassword
(anonymous)	@	createMetaRPCHandler.js:23
```

- Without removing the extension from the browser, switch to this PR
branch and build again
- Visit [chrome://extensions/](chrome://extensions/) and reload the
extension
- Try to login again, you should be able to access the wallet again

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

<!-- [screenshots/recordings] -->

<!-- [screenshots/recordings] -->

- [ ] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask
Extension Coding
Standards](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [ ] I've completed the PR template to the best of my ability
- [ ] I’ve included tests if applicable
- [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [ ] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.

Co-authored-by: Michele Esposito <34438276+mikesposito@users.noreply.github.com>