Add i18n support for translations

[cesar-ayar]

🔖 Feature description

Add i18n support to allow easy translation into other languages.
This will enable Postiz to be translated and expand its reach.

🎤 Why is this feature needed ?

OSS often reaches out to the entire world, so it is a useful idea to start translation work to make it available in other languages.

✌️ How do you aim to achieve this?

I want this feature to simplify the use of Postiz for the Spanish-speaking community, by adding it to many other communities with the support of translators.
To do this, it will make the text strings dynamic using i18n

🔄️ Additional Information

Using i18n to handle dynamic text strings

👀 Have you spent some time to check if this feature request has been raised before?

• I checked and didn't find similar issue

Are you willing to submit PR?

Yes I am willing to submit a PR!

[nevo-david]

Do you have a suggestion for the solution?
Should we just use nexti18?

[cesar-ayar]

That's right, we can start by implementing i18n, additional for a visual flow you can use Crowdin.

Many platforms use i18n as a method of internationalization, Cal.com is one example of this.

I would be happy to start implementing i18n.

[nevo-david]

I prefer to use Tolgee.
But I don't want to use an additional system, maybe a simple translation is better.

[nevo-david]

next-intl

[cesar-ayar]

This is great, here could you clarify for me, would it be using i18n or just next-intl?