tests: Document expected parse task

tests: Use static tokens with static locattions

tests: Document parse error exception codes

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

tests: Clean up syntax and parse code

tests: Clarify function documentation

tests: Optimize and move draw_syntax_not_token to tests_syntax ...

Drawing random tokens and throwing them away was killing test
performance.

tests: Refactor mid-test assumes in to custom draws ...

This should help with performance as Hypothesis as we no longer need to
do complex unrelated draws first.

tests: Random insert_random to insert_random_within

parse: Handle parent_context in template_parse_invalid

tests: Fix some typos for text tests

tests: Split up parser tests for empty cases

tests: Use one test per invalid case for text and notes

tests: Add template_parse_invalid

tests: Move insert_random to parse.templates

tests: Add a template for parsing valid syntax

parse: Have parse_text handle contexts properly

parse: Allow attaching a ParseContext to a ParseErrorException

tests: parse: Move text tests to its own file