chore: add more translations

[he0119]

tried my best to find translatable strings.

there maybe some duplicate strings, don't know if they should be merged together.

assisted by i18n-ally.

{
  "i18n-ally.languageTagSystem": "legacy",
  "i18n-ally.localesPaths": "strings/languages/",
  "i18n-ally.pathMatcher": "{locale}/strings.json",
  "i18n-ally.keystyle": "nested",
  "i18n-ally.preferredDelimiter": ".",
  "i18n-ally.enabledFrameworks": ["react-i18next"],
  "i18n-ally.sourceLanguage": "en",
  "i18n-ally.displayLanguage": "zh-CN",
  "i18n-ally.extract.autoDetect": true,
  "i18n-ally.regex.usageMatch": [
    "[^\\w\\d]getString\\((?:\\s+)?['\"`]({key})['\"`]"
  ],
  "i18n-ally.refactor.templates": [
    {
      "templates": ["getString('{key}'{args})", "{getString('{key}{args}')}"]
    }
  ],
  "i18n-ally.editor.preferEditor": true,
  "i18n-ally.sortKeys": true
}

[nyagami]

I know it's too late to change. But do you think getting strings to translate by screens is a gud solution ? @rajarsheechatterjee .
screenName.subScreenName.someAction.
What if the module is changed. the tranlated strings will be dropped right?

[rajarsheechatterjee]

I know it's too late to change. But do you think getting strings to translate by screens is a gud solution ? @rajarsheechatterjee . screenName.subScreenName.someAction. What if the module is changed. the tranlated strings will be dropped right?

I initially used this so the context of the string is there while translating. It might not be necessary and also it's making the keys really long. Going forward we can add newer strings directly instead of nesting it.

[he0119]

I initially used this so the context of the string is there while translating. It might not be necessary and also it's making the keys really long. Going forward we can add newer strings directly instead of nesting it.

Maybe I should rename the keys right away in this PR.

[nyagami]

LGTM, thanks