Added Korean language support (#1596)

Added Korean language support.

<img width="860" height="274" alt="image"
src="https://github.com/user-attachments/assets/e726d910-81cb-4cc7-8062-18f04592332f"
/>

To ensure accurate meaning, some terms were written following the
criteria below.

- Map → '맵' : 'Map' is rendered as '맵', which is more commonly used than
'지도' in GIS tools.
- Stops → '기준점' : Transliterating the term as '스톱' does not clearly
convey its meaning. Since it represents a reference point used for
interpolation, it is translated as '기준점'.
- Light → '라이트' : Literal translations such as '광원', '빛' or '조명' awkward
in a 3D rendering context, so the term is transliterated.
- Focus → '포커스' : The literal translation '초점' sounds awkward in a UI
context, so it has been transliterated for clarity.
- Terrain → '터레인' : In the context of 3D maps, '터레인' is a more commonly
used term than '지형'.
- Paint → '페인트' : The term is transliterated to preserve its meaning as
defined in the Style Specification.

---------

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Co-authored-by: Harel M <harel.mazor@gmail.com>

i18next-parser.config.ts

@@ -1,6 +1,6 @@
 export default {
   output: "src/locales/$LOCALE/$NAMESPACE.json",
-  locales: [ "de", "fr", "he", "it","ja", "zh" ],
+  locales: ["de", "fr", "he", "it", "ja", "ko", "zh"],
 
   // Because some keys are dynamically generated, i18next-parser can't detect them.
   // We add these keys manually, so we don't want to remove them.