Tests for alternate language templates

[ianthetechie]

Currently the test suite only covers the "default" template for each country. However, there are some cases where the template should also be localized based on language. For example, the formatting and component order is different when writing a Korean address in "English" (somewhat debatable if that's the correct descriptor I suppose but setting that aside... there are clearer cases too).

We have templates for this but don't currently test them.

A magic component name like "language" or maybe "variant" is the easiest way I can think of to solve this short term.

You guys probably know better than I if this is the best way to model it, but I'm just going with the assumption that it's "language" for now. But I think some special fallback values like "latin" or "other" make sense too. I assume most libraries currently hard code English as a fallback for cases like Korea and Japan.

[ianthetechie]

I'm actually wondering now if we should move this to a meta key. The "abbreviate" behavior is also tested in the current suite, but it's not explicit; implementations just need to know that if it's in a specific directory, enable abbreviations. Putting language variant, abbreviation, and anything else in tho future under a meta key would create a clear line between what's supposed to be treated as an address component and what's just modifying test behavior.