Chrome encodes/decodes based on user terminal

Uses Term::Encoding heuristics to identify the terminal encoding
and encodes prompts/defaults and decodes responses.
fix prereqs to match next release number
make tester slurp_file return text

...and add a raw version just in case
non-ASCII dist corpus for testing
first draft of file role with encoding support
have File::OnDist use Path::Tiny to slurp raw
improve various error handling issues for file encoding
fix text/bytes mode for some file injectors
write out encoded, not stringy, content
omit an erroneously passed argument
switch MetaJSON callback to returning bytes

(as xdg originally intended)
open file raw instead of opening then binmoding
when decoding a file, call "decode"

not "encode"
distmeta tests for non-ASCII authors
assume that Tester add_files files are text strings
add a bit of non-ASCII text to generated file tests
test for non-ASCII author in generated LICENSE file
non-ASCII author tests for NextRelease

when desk checked, this found a nice nasty bug earlier today!
use encoded content to get md5 sum of document
non-ASCII copyright holder test for README file