Change i18n tooling to `lingui`

[adamsoderstrom]

Change i18n tooling to lingui

Pros

• Works with SWC and Babel. Gives us compatibility for Storybook.
• Possibility to generate catalog files based upon i18n usage in component files.
• Validation of translation coverage

Cons

• Little bit bigger footprint than the one currently used (es2015-i18n-tag) (3.4kb vs 2.4kb).
• A bit unsure if it supports the JSON structure create-ignite-app is using today. May be possible through some configuration. Though, they have a pretty nice alternative, where you have one translation files per component. Though, these are just examples. We should strive for keeping the current pattern and then reconsolidate if another one would be better.

[adamsoderstrom]

Tried to set it up with a fresh instance of create-ignite-app, but got blocked because of https://github.com/lingui/js-lingui/issues/1401. Will retry when that issue gets resolved.

[andrii-bodnar]

Hi @adamsoderstrom, the issue should now be resolved in v3.17.2, could you please try it?

[adamsoderstrom]

Hi @andrii-bodnar ! Thanks for reaching out! Will try it out! 😊

[maeertin]

This look really promising! Let's investigate how we can get a complete SWC setup while keeping a working Storybook environment :)

[maeertin]

Closing PR as no longer relevant as "cia" is now purely a documentation app.