feat(multichain-account-service): filter KeyringController locked errors from sentry reporting

[hmalik88]

Explanation

There's instances where we can hit keyring controller is locked errors, we should not be reporting those. Added a function to determine if an error is a keyring controller locked error and used that to prevent sentry reporting.

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 communicated my changes to consumers by updating changelogs for packages I've changed
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

---

Note

Low Risk
Low risk: only adjusts error classification for Sentry capture, treating KeyringController "ControllerLocked" as a warning like timeouts and adding tests around the new behavior.

Overview
Prevents noisy Sentry reporting by treating KeyringControllerErrorMessage.ControllerLocked errors the same as TimeoutError: they are now logged as warnings and not sent to captureException.

Adds isKeyringControllerLockedError to providers/utils, updates reportError to use it, and introduces unit tests covering both the new predicate and the updated reporting behavior; changelog is updated accordingly.

^{Reviewed by Cursor Bugbot for commit 9aea456. Bugbot is set up for automated code reviews on this repo. Configure here.}