[BEAM-2976] Analytics added to MS, cleanup

[Leinnan]

Ticket

Brief Description

Checklist

• Have you added appropriate text to the CHANGELOG.md files?
• Is there an appropriate JIRA ticket number, and is it named in the title?
• Have you documented all your public methods and interfaces? Have you identified intention and assumptions?
• Have you included a docs file as /wiki/BEAM-1234.md? You need to provide a docs file.
• Does this introduce tech-debt? If so, have you added an entry to the Tech-debt document?

Notes

When you are merging a feature branch into main, please squash merge and make sure the final commit contains any relevent JIRA ticket number. If you are merging from main to staging, or staging to production, please use a regular merge commit.

[github-actions]

Have a WebGL build, friend. 7a52dc1c53403da8a130a6e9bf496fda7f4a6286

[github-actions]

Have a WebGL build, friend. 4692417aab2e9bbf14905561740d836081af7502

[cdhanna]

We hit a snag very similar to this when we did the 1.3 release- moving some of the classes out of the Beamable core runtime asmdef and into the common asmdef caused backwards compat issues.

I guess I don't really see a way around it, but it may mean we need to 2.0 this?