Support for translation/internationalization

I think this is probably a long ways down the line to actually support, but could be worth some thought now so we don't architect things in a way that prevents this.

There are some very easy things we can do now:

- CLI level - wrapping output in a t() type function that could be later used to translate the application based on user LOCALE
- Catalog/content/templates - incorporating an `en` into the filename format and avoiding hard coding strings in the application (since you might want to produce a non-english VPAT with an english CLI configuration)