Start tracking 'canonical properties'

[LPGhatguy]

This PR is a robust solution for #18, #14, and is a step towards #16.

This change introduces the idea of a canonical property more concretely. This idea helps us map from serialization-specific names onto common names that projects can agree on for referring to the same idea.

The concept for property canonicalization came out of Rojo, and seeks to handle these cases:

1. Some properties have deprecated aliases, or aliases used only for serialization, like Fire.Size
2. Some properties are scripted through special getters/setters, like CollectionService tags
3. Some properties are not scriptable, but specified in the disk formats, like Lighting.Technology

A new file was added to generate_reflection called canonical-properties.toml that specifies these relationships. Previously, these ideas were present in rbx_xml's ad hoc reflection database, but they're needed for rbx_binary as well.

There are a couple of assumptions that this approach makes:

1. Most properties in the API dump are scriptable and have the same name and type when serialized
2. Most properties that don't follow (1) are just aliases of other properties

While I'm sure about (1), there are non-trivial cases where (2) doesn't hold up. The most notable example is part color, which used to be BrickColor, but is now Color3uint8, which requires a name and type conversion to Color3 before it can be reflected to Lua.

[LPGhatguy]

It's mostly ready, I think!