parse: Reserve keywords for reference names

parse: Parse a reference node

src: Rename syntax to token

parse: Remove SyntaxType ...

Once again I find myself in the pattern of having a useless 'type' value
that just complicates my life. In this case the correct appproach is to
output the AST directly.

parse: Parse text and bools to AST types

parse: Check types when clearing notes, add extra tests

parse: Pass a context to the parse function

parse: Have parse_text handle contexts properly

parse: dNonnescent -> descent ?

parse: Have parse_bool handle contexts properly

parse: Use an error context for clear_notes

src: Pass a parent context to skip_note

parse: Have skip_note create a PARSE_NOT ParseContext

parse: Use __repr__ instead of __str__

parse: Pass a ParseContext to read_token

parse: Allow attaching a ParseContext to a ParseErrorException

parse: Add parse contexts for later error reporting

parse: Clear notes as first parse step

parse: Add clear_notes function to handle removing comments

parse: Put skip_note in its own class for testing

parse: Wrap parse functionality to allow mock testing

parse: Parse boolean values

parse: Add skip_note for parsing notes

parse: Add ParseError and ParseErrorException for error reporting

parse: Ignore whitespace in text, instead join words with spaces ...

This cuts down on complexity as now only the tokenizer deals with
whitespace and makes whitespace no longer a factor in the language.

tokenize: Move syntax to its own module

parse: Add read_token function

parse: Move Syntax to tokenize and replace Token ...

These are basically the same classes so merge them

parse: Don't nest tokens in values ...

Now that we don't need to copy the TokenType we can just copy the value
directly.

tokenize: Remove TokenType enum ...

In practice this wasn't used: The parse code always checks the value AND
the type. So just check the value only.