Add internationalization package

[mdubya66]

We need to get i18n system in place before we get too far down the debt hole

[mdubya66]

for MVP we have agreed to be internationalized. localized is not an MVP requirement.

[andrewtchin]

https://github.com/nicksnyder/go-i18n
https://github.com/maximilien/i18n4go

[mdubya66]

I looked at both and they seem more for extracting strings in order to localize them. What we need here is basic message catalog infrastructure and some best practices around using it, I think.

I found this https://godoc.org/golang.org/x/text/message

It says it's under construction and points to design proposal which I can't seem to access.

[mdubya66]

golang/go#12750 is the actual golang issue where it is being discussed

[dougm]

After we get the wrapper in, we need to identify messages we want to internationalize. GUI/CLI labels that are displayed to the user seems to be the most likely place to start, such as CLI flags usage strings. Not so obvious to me is log messages.

And for distributing the log message bundles, we need a way to include these files either inside the binaries or along side them. Likely another wrapper method to locate and load said bundles. Note that it is possible to include files inside the compiled go binaries. There are several packages out there to help with this, I also have a simpler version internally if we decide to go this route.

[andrewtchin]

Created follow on issue to use the new package #245