Clarify the ability for basic pipeline tooling to parse and produce UTF-8 in files

[kltm]

With the recent discussion on whether or not to include UTF-8 in the GPAD/GPI 2.0 spec, we feel that it is important to know if the basic parser and emitter functionality supports UTF-8 already, and if not how much additional work it might be to support it.

Closing this ticket would include clarifying basic clarifying information for GAF input and output. Most likely using go rule 0000001 GAF line i/o checks as a proxy.