fix: skip no-op AssetsController state assignments

[salimtb]

Explanation

Repeated asset polls often return the same metadata, balances, and prices as objects with new identities. #updateState assigned those values unconditionally, so Immer recorded patches even when every field was already in state. BaseController.update() then published stateChange, which hosts persist.

This skips assignment when the computed next value is deep-equal to the current slice. No-op polls no longer produce patches or stateChange; a real amount/price/metadata change still publishes once.

References

N/A — host-side persistence cost from identical AssetsController updates.

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

Made with Cursor