External table files

All 14 scenarios passing

A table can live in a classpath resource file instead of the annotation: @TableTest(resource = "external.table", encoding = "UTF-8"). The first three rules below call the loading API with those same arguments, so the tables can show which paths resolve, what text the file's bytes become, and how loading fails; the rules after them are driven by the very files shown, each row coming from a line of the file rather than from the annotation.

A resource path resolves from the classpath root, with or without a leading slash
A resource that cannot be read fails with a message naming the file
A table loaded from a resource file runs like an inline table
Resource files can declare a non-default character encoding
The declared encoding decides what the file's bytes become