feat(account-tree-controller): force-init before any account insertion/removal

[ccharly]

Explanation

We now enforce that init got called before making any change to the tree to avoid having out-of-order account groups.

I stumbled upon this bug when running E2E on mobile. Basically, the way the fixture are setup on mobile were triggering :accountAdded before calling AccountTreeController.init, which resulted in having "Account 2" inserted before "Account 1".

But, since "Account 1" was already part of the initial internalAccounts it should have been inserted before any new accounts.

Thus, forcing init to be called implicitly fixes this order/sequence.

References

E2E were failing on this PR, because of this bug:

• chore: bump multichain accounts deps metamask-mobile#20255

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, highlighting breaking changes as necessary
• I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes