Use bespoke exception classes

[Chris Fuller]

We’re currently using IllegalArgumentException and IllegalStateException in somewhat haphazard ways. Ideally, we would instead:

• Have our own dedicated exception classes
• Use individual exception classes that are specialized so that they can be distinguished without parsing the message
• Provide information about where the error occurred, if possible, meaning a line/column of the source doc, an xpath/jq-style locator, etc.

‌

[Chris Fuller]

Fixed in 0.6.0