[Website] Fix Google Translate functionality for non-default languages

[zooo-code]

Description

Currently, the official website supports multi-language switching via the navigation bar. However, when switching to languages supported by Google Translate (e.g., Japanese, Korean, French, Spanish, Russian, Deutsch), the page content is not translated into the target language.

It seems that the Google Translate widget is not triggered correctly or the language code mapping is failing.

This issue was identified and discussed with @davidzollo in #10289.

Reproduction Steps

1. Go to https://seatunnel.apache.org/
2. Hover over the language dropdown in the navigation bar.
3. Select a non-default language (e.g., 한국어 or 日本語).
4. Observe that the page content remains in English/Chinese and does not translate.

Expected Behavior

When a user selects a language from the dropdown, the Google Translate widget should activate and translate the page content into the selected language.

Are you willing to submit PR?

• Yes I am willing to submit a PR!

[DanielCarter-stack]

Thank you for reporting this issue and being willing to contribute a fix!

After checking the repository, I found that the main apache/seatunnel repo contains documentation content (.asf.yaml homepage: https://seatunnel.apache.org/), but the website frontend code integrating Google Translate is not located here.

A search for Google Translate integration code returns 0 matches in docs/ and across the entire codebase. Apache projects typically host website code in a separate asf-site branch or an independent repository (neither of which currently exists in this repo).

Before submitting a PR, could you help confirm:

1. Where is the SeaTunnel website frontend code hosted? (e.g., separate repository, CI/CD build pipeline)
2. Are you referring to https://seatunnel.apache.org/ deployed content, or a local development setup?
3. Can you share a screenshot or the browser console errors when switching to non-default languages?

Once we locate the correct repository containing the website's JavaScript/HTML and Google Translate integration, we can provide concrete guidance on fixing the language switching logic. You may also want to reach out to @davidzollo mentioned in the related discussion.