[FRAME-156]: Add Events

[tarecord]

This adds the ability to trigger specific events with a do_action() so additional data can be collected from sites when users perform specific actions.

[ChrisMKindred]

This all looks good. Should we look into using version/tag branches so you don't have to use the TBD in the since param? I am concerned that merging directly to Main without a version branch could result in that TBD getting left in before a deployment.

[tarecord]

Yeah, that's a good point and I thought the same thing.

Now that this has been released, should we move to a more strict gitflow workflow:

• Set up a new develop branch as the default
  • New development is merged directly into this branch
• Use specific release branches to prep releases
  • Once we decide we're ready for a new release, these are used to prep and merge into main
  • This would be where we update all @since TBD instances to the current release

[ChrisMKindred]

I recommend creating a contributing.md file with the details so that it is well documented. GitHub will highlight this file for you when people are making new contributions making it clear what the expectations are.

[tarecord]

Hey @ChrisMKindred, here's a link to the subset of most recent changes that should make it a little easier to see what I did.

Mainly two things:

• Moved event-related methods from Telemetry.php to Event.php
• Updated the Telemetry::send() method to check if the site is currently opted-in before sending

Let me know if you have any questions or suggestions.

[ChrisMKindred]

Looks good and is fine to merge. Could we add the mocking as a setup function? It is repetitive for us to create the array and function mock in each test.