Use rbx_reflection to allow type inference on projects

[LPGhatguy]

This is one step towards resolving #31.

This change starts using rbx_reflection's reflection database and type resolution mechanisms to make specifying projects less painful.

This is a dependency that will need continual upgrades in order to support specifying new properties with this short, inferred syntax.

Previously, you would specify a project with properties on services like this:
_{(diff markers added to draw attention)}

{
	"name": "really-red-place",
	"tree": {
		"$className": "DataModel",
		"Lighting": {
			"$className": "Lighting",
			"$properties": {
+				"Ambient": {
+					"Type": "Color3",
+					"Value": [1, 0, 0]
+				},
+				"Technology": {
+					"Type": "Enum",
+					"Value": 1
+				}
			}
		},
		"HttpService": {
			"$className": "HttpService",
			"$properties": {
+				"HttpEnabled": {
+					"Type": "Bool",
+					"Value": true
+				}
			}
		}
	}
}

But after this PR, Rojo can use the reflection database to infer types where they should be obvious:

{
	"name": "really-red-place",
	"tree": {
		"$className": "DataModel",
		"Lighting": {
			"$className": "Lighting",
			"$properties": {
+				"Ambient": [1, 0, 0],
+				"Technology": "Voxel"
			}
		},
		"HttpService": {
			"$className": "HttpService",
			"$properties": {
+				"HttpEnabled": true
			}
		}
	}
}