Feature: Linting for IDL code

[znorman-harris]

Now that we have patterns for validating syntax, populating and validating types, can we extend this to plug-and-play rules for how you should write your code?

For example, be able to do things like:

• Make sure functions/procedures are pascal/camel/snake case
• Force the use of "on_error" at the top level of the bottom file in a routine
• Ensure logic blocks use "begin...end"
• etc.

We would also need to make sure that our naming convention is squared away to not be confused with actual syntax errors we detect.

This would also need to have auto-fix and ways to configure.