[FEAT] Addition of an OR operator for types

[Calamixy]

Describe your feature

The addition of an OR operator for types will create better data definitions with less overhead, compared to tagged enum alternatives. The operator can function similar to Luau i.e. type bool_or_u8 = boolean | u8

Alternatives

Using tagged enums will in essence function as an OR, however there is more overhead.
i.e.

enum "Type" {
    Number {
        Value: f64,
    },

    String {
        Value: string,
    },
}

WILL CREATE -->

({
	Type: "Number",
	Value: (number),
} | {
	Type: "String",
	Value: (string),
})

meaning that there is now an overhead of both a string and the value's type.

[sasial-dev]

Implimentation Details:

• OR would have | syntax like type Test = f64 | string
• OR should parse to a list not a tree
• OR would only work for primatives
• OR will error if two types of numbers are added to the list
• OR can be optional like type Test = (f64 | string)?.

[sasial-dev]

This issue will be done with the convert rewrite - expect it in 0.7.0.