Make coloring recursion guard actually work properly

Previously, the guard would set coloring to NO when it tripped. Another recursion would then cause the guard to not work.
Separate syntax marking from syntax coloring

This is now done in two separate passes.
Correct indentation

Was previously not corrected to keep diffs sane
Remove dead code
Modernize primordial exception handling
Remove last reference to now-unused defaults key
Extract an ASKSyntaxColorist object from ASKSyntax
Correct credits on ASKSyntax and friends

All UKSyntaxColoredTextViewController code has been extracted from ASKSyntax, so move those copyright statements and licenses over there.
Start moving away from directly accessing syntax definitions
Create an ASKSyntaxComponent class

Doesn't actually do anything yet, but we now know where we'll need to use it.
Use properties to access data in ASKSyntaxComponent
Move some of the actual marking logic into an ASKSyntaxComponent category

This will soon allow me to reduce the amount of crap being passed around.
Depend on properties, not parameters, in ASKSyntaxComponent(Marking)
Improve variable naming in ASKSyntaxComponent (Marking)
Hoist exception handling out of individual markWhatever: methods

Also logs said exceptions.
One more variable name in ASKSyntaxComponent (Marking)
Rework coding style of ASKSyntaxComponent (Marking)
Mark *only* the indicated range

Also updates coding style of ASKSyntaxMarker
Attribute string with syntax components, not names

Allows us to remove hacky loop and improve several other things.
Extract a "color palette" object and use it to look up colors