feat(i18n): update zh-Hans translations

[PaiJi]

This PR focus on add zh-Hans translation for common UI(sidebar) mostly.

[PaiJi]

Fixing: #1429 (review)
Fixed in 261f144

[PaiJi]

CI lint-and-typecheck task failed since this PR: #1508
@Siumauricio

[PaiJi]

Not sure if the practice of putting all translations in the same file will significantly slow down our page loads, since the hydration data will now contain two translation files for the locale. What do you think? @Siumauricio

[Siumauricio]

You are right @PaiJi , it can lead to large json file transfers in SSR,

[PaiJi]

You are right @PaiJi , it can lead to large json file transfers in SSR,

So what's our plan? using this solution for now, until we refactor the dashboard with tanstack (I just read in another issue that you're considering refactoring to tanstack)?

[Siumauricio]

You are right @PaiJi , it can lead to large json file transfers in SSR,

So what's our plan? using this solution for now, until we refactor the dashboard with tanstack (I just read in another issue that you're considering refactoring to tanstack)?

Yes, for the moment you can leave it as it was using separate json so that the json download is not so big,

regarding the migration to tanstack, if it is something I've been seeing for a couple of months, it is what most resembles nextjs and work integrations like trpc, better auth and many things very easily, besides we would be using vite which is three times faster than what nextjs currently offers, so if this is in my plans, I'm just waiting for tanstack remove vinxi, and is even much lighter to create a plan for migration

[PaiJi]

You are right @PaiJi , it can lead to large json file transfers in SSR,

So what's our plan? using this solution for now, until we refactor the dashboard with tanstack (I just read in another issue that you're considering refactoring to tanstack)?

Yes, for the moment you can leave it as it was using separate json so that the json download is not so big,

regarding the migration to tanstack, if it is something I've been seeing for a couple of months, it is what most resembles nextjs and work integrations like trpc, better auth and many things very easily, besides we would be using vite which is three times faster than what nextjs currently offers, so if this is in my plans, I'm just waiting for tanstack remove vinxi, and is even much lighter to create a plan for migration

Just to confirm, I'm going to continue to keep the translation files for the individual pages in a different json (i.e. roll back your changes) until we rewrite to tanstack or something else.