tests: Document expected parse task

tests: Test parse_value error propagation

parse: Add code for parsing values

tests: parse: Clarify what error_on_token does

tests: parse: Use a mock class for note skipping

tests: Use a static parse context for tests

tests: Use a static token location for random tokens

tests: Use static tokens with static locattions

tests: Use static token location for tokenizer test

tests: Fix test reference invalid name

tests: Fix test_tokenize not testing whitespace ...

This relied on draw_token_random which now doesn't include whitespace

tests: Document parse error exception codes

parse: Reserve keywords for reference names

tests: Move whitespace code to test_tokenize ...

The parser doesn't have to worry about whitespace, so it's not worth
worrying about it here.

parse: Parse a reference node

tests: Add garbled strategy for draw_token_random

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

syntax: Refactor draw_syntax_random and add draw_syntax_texttoken ...

I realized draw_syntax_classified is the same as draw_syntax_random, so
just merge them.

Also add draw_syntax_texttoken explicitly meant to weed out cases where
token type is not set.

tests: Clean up syntax and parse code

tests: Clarify function documentation

tests: Tweaks to health checks and examples ...

The time-based health checks keep causing transient test failures,
especially when my host system is under load. Throw them away.

Also drop the max examples for long down. CI is already taking an hour,
so I assume long is going to take days.

tests: Fix name for draw_syntax_not_token

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

tests: Refactor clear_notes tests

parse: Handle parent_context in template_parse_invalid