Frontmatter Schema Simplification

[AsherGlick]

Hopefully this is a simplification. JSONSchema is just really terrible in general for what we are trying to do. However it still has some uses when it comes to validation. This is just a wrapper around how the JSONSchema is generated so that we reduce mistakes.

When the old schema and the new schema were exported as json objects this was the diff between them:

--- old_schema.json	2023-09-29 23:08:11.147771543 -0500
+++ new_schema.json	2023-09-29 23:08:11.147771543 -0500
@@ -12,8 +12,8 @@
                 "MultiflagValue",
                 "Enum",
                 "CompoundValue",
-                "Custom",
-                "CompoundCustomClass"
+                "CompoundCustomClass",
+                "Custom"
             ]
         }
     },
@@ -611,9 +611,10 @@
                     "compatability",
                     "xml_fields",
                     "protobuf_field",
+                    "class",
                     "xml_bundled_components",
                     "xml_separate_components",
-                    "class"
+                    "components"
                 ],
                 "properties": {
                     "type": {

This diff shows that the only things that changed were the ordering of Custom and CompoundCustomClass in the global type variable limiter enum. This change is desirable because now the order that is in the enum limiter is the same order as the checks appear.

The other diff shows a similar movement of a field in the CompoundCustomClass schema definition of the value class which also now aligns with its ordering in the properties. Additionally the final diff shows that we had missed adding "components" as a required field to the CompoundCustomClass meaning that this change has already been able to catch a user error, caused from needless manual repetition.