fix event names

[ndurell]

Description

We used inccorect event names in some cases. This should fix the names to be more in line with other Klaviyo SDKs. These names will also look better in Klaviyo.

Check List

• [x] Are you changing anything with the public API?
• [ ] Have you tested this change on real device?
• [ ] Are your changes backwards compatible with previous SDK Versions?
• [ ] Have you added unit test coverage for your changes?
• [ ] Have you verified that your changes are compatible with all the operating system version this SDK currently supports?

Manual Test Plan

1.

Supporting Materials

[evan-masseau]

Maybe worth adding "missing" types in the same release https://github.com/klaviyo/klaviyo-swift-sdk/issues/119

[evan-masseau]

Would this work for namespacing the event names?

public struct Event: Equatable {
    private enum EventName: Equatable {}

    public struct V1 {
        public enum EventName: EventName {
            case OpenedPush
            case ViewedProduct
            case CustomEvent(String)
        }
    }

    public struct V2 {
        public enum EventName: EventName {
            case OpenedPush
            case ViewedProduct
            case CustomEvent(String)
        }
    }

and

extension Event.V1.EventName {
    var value: String {
        switch self {
        case .OpenedPush: return "$opened_push"
        case .ViewedProduct: return "$viewed_product"
        case let .CustomEvent(value): return "\(value)"
        }
    }
}

extension Event.V2.EventName {
    var value: String {
        switch self {
        case .OpenedPush: return "$opened_push"
        case .ViewedProduct: return "Viewed Product"
        case let .CustomEvent(value): return "\(value)"
        }
    }
}

[evan-masseau]

Never mind, my XCode was broken, that idea doesn't even compile

[evan-masseau]

This PR needs to be split up now, into a non-breaking deprecation for a minor version release, and a breaking change for major release.

[ajaysubra]

This PR needs to be split up now, into a non-breaking deprecation for a minor version release, and a breaking change for major release.

I can help with this if you have not already started on it.

[evan-masseau]

Superceded by #138 and #139