fix: Add enum types for commerce event

[Mansi-mParticle]

Instructions

1. PR target branch should be against development
2. PR title name should follow this format: https://github.com/mParticle/mparticle-workflows/blob/main/.github/workflows/pr-title-check.yml
3. PR branch prefix should follow this format: https://github.com/mParticle/mparticle-workflows/blob/main/.github/workflows/pr-branch-check-name.yml

Summary

• Added enums for e-commerce events.
• 'expandProductAction' to create an event instead of a transaction. Separate it into different e-commerce event types.

Testing Plan

• Was this tested locally? If not, explain why.
• Tested it with a sample application and ran unit tests

Reference Issue (For mParticle employees only. Ignore if you are an outside contributor)

• Closes https://go.mparticle.com/work/[SQDSDKS-6551

[samdozor]

let's chat about another way to approach this, i'd like to understand the problem better.

[samdozor]

this would be an incorrect public api change that'd likely cause a lot of pain and bugs :-) please revert

this enum is the one for custom events. it isn't meant to be used for all event types. ios does it this way and it's been a bug and complaint for years - customers for example log regular custom events with incorrect event types.

create some other private enum if we need it internally? these enum values shouldn't be exposed to customers.

[samdozor]

and this is exactly what customers do and is not correct. then we end up with weird data, broken filtering, integrations, etc.

MPEvent is custom event and cannot have AddToCart (or any of the others below) as a custom event type in our schema.