SPIKE: Centralizing country and language data in stripes components

Overview:
Would like to write a few stories about centralizing country and language data in stripes-components but want to check in with Thunderjet first. Maybe there are legit reasons for stripes-acq-components to maintain its own lists for these data?

Background:
It seems like the list of languages in various places in FOLIO UI is data - or Localize - driven these days instead of using the old languages.json file.

We have a client that need to add language codes to this list from the iso639-3 standard (one example: https://iso639-3.sil.org/code/yue) and I am sure there are other lists around the corner as well

Scenarios:
TBD

1. Scenario:
   • Given <preconditions>
   • When <actions>
   • Then <results>
2. Scenario:
   • Given <preconditions>
   • When <actions>
   • Then <results>