feat: implement MM Connect Multichain Analytics

[ffmcgee725]

Explanation

This PR implements all of the remaining events/properties found in the event’s schema that are not yet in the mm-connect package.

References

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

[adonesky1]

Sorry if I missed this in our earlier call, but shouldn't this be a global property rather than a discreet event? Lets loop back w/ @adamceresko since I think we may want to fully remove the mmconnect_initialized event since I think it will be mostly noise (it will happen on every page load where MMConnect is installed)

[ffmcgee725]

After convo with @adamceresko, he preferred to keep this initialized event in, but you can sync and we loop back to this.

[adonesky1]

Ok. I'll loop back with him on this. But in any case I'd think dapp_id should be a global property no?

[ffmcgee725]

https://github.com/MetaMask/connect-monorepo/blob/66e8f8200277b018b7679f929eb0cf428b08ddf4/packages/connect-multichain/src/multichain/index.ts#L209C1-L210C1

☝🏾 it actually is, the test file property value is just misleading

[ffmcgee725]

changed here 683fec5