feat: add JSON lint check for i18n folder

[davutkilic]

Comprehensive Summary of your change
Added a new GitHub Actions workflow (json-lint.yml) to validate all JSON files in src/portal/src/i18n/.
This ensures any malformed JSON will cause the CI to fail, preventing invalid translations from being merged.
Issue being fixed
Fixes #21685

Checklist
Well Written Title and Summary of the PR
Example: “feat: add JSON lint check for i18n folder”
Label the PR as needed
Choose an appropriate label such as release-note/new-feature or release-note/enhancement.
Accepted the DCO
Make sure all your commits include the Signed-off-by: Your Name [email protected] line.
Tests are passing and test coverage is added if needed
The JSON lint check is run in the new workflow.
Docs impact
No separate docs change needed, since this is an internal CI improvement.

[reasonerjt]

Could you write the comment in English?

[davutkilic]

Translated it into English

[bupd]

We can already have this just by introducing a new plugin to es lint. and let the lint take care of this rather than having a new CI workflow for checking json.

[bupd]

Please add the below to the .eslintrc.json

    {
      "files": ["*.html"],
      "excludedFiles": ["*inline-template-*.component.html"],
      "extends": ["plugin:prettier/recommended"],
      "rules": {
        "prettier/prettier": ["error", { "parser": "angular" }]
      }
    },
+    {
+     "files": ["*.json"],
+      "extends": [
+        "plugin:json/recommended-legacy",
+        "plugin:prettier/recommended"
+      ],
+      "rules": {
+        "json/*": ["error"],
+        "prettier/prettier": ["error", { "parser": "angular" }]
+      }
+    }

Hope this helps

[bupd]

Also don't forget: npm install eslint-plugin-json
Adding a lint rule as suggested above would easily fix this issue.

Thanks