Full i18n Support

[pgfisico]

FRC is international, so it would be a nice touch if the tools could be easily translated, whether officially or by the community.

• It's easier to build the support now. Even if the UI is all English right now, it's easier to do this now rather than finding all the UI strings later.
• The process for translating and contributing translations can be defined at a later time
• Anything exposed to the user should be supported (in rough descending priority)
  • UI elements and messages
  • Webviews
  • Extension Marketplace metadata
• No need to internationalize logging
• Fallback to English if no translation exists

See also:
#68

[ThadHouse]

This would likely be a community thing. We don't really have the resources, however we would be happy to accept PRs, like happened with 68.

[moesoha]

REALLY SORRY for that!

Previously it's me who add i18n support at first. I'm a Chinese senior high school student at that time. As you know, Gaokao (or National College Entrance Examination) is veeeeeery important. I was turning to my study after my first i18n PR.

In fact I did more translation work in https://github.com/moesoha/vscode-wpilib/tree/im-i18n-1 , but it fell far behind the current master, I gave it up.

I'm in my fresh year now, and I will restart the i18n work recently. There are some details to be confirmed and I have these idea below.

• Use English directly as our i18n key (except i18n in Command Palette, just keep the present code)
• Use a template engine such as ractivejs/ractive or even vuejs/vue to render i18n in WebView

@ThadHouse Can you add me as a collaborator? I want to open a branch in this repository and do the work in this repo.

[moesoha]

• UI elements and messages
• Webviews

Full support of the two are implemented in #271