HDDS-9571. Enable Docusaurus i18n support

[will-sh]

What changes were proposed in this pull request?

HDDS-9571. Enable Docusaurus i18n support

This pull request enables Docusaurus internationalization support for Simplified Chinese on the Apache Ozone Website v2 branch.
The patch adds zh-Hans to the Docusaurus locale configuration, defines locale metadata for English and Simplified Chinese, and generates the initial Docusaurus translation scaffold under i18n/zh-Hans. It also provides initial Simplified Chinese translations for core website UI labels, including the navbar, footer, blog options, built-in theme strings, and documentation sidebar category labels.

The goal is to enable the Website v2 i18n framework so the site can expose Chinese locale routes such as /zh-Hans/. This patch does not attempt to translate every Markdown or MDX content page. Full Chinese documentation translation or migration can be handled incrementally in follow-up patches.

What is the link to the Apache Jira?

https://issues.apache.org/jira/browse/HDDS-9571

How was this patch tested?

The patch was tested with the following commands:

pnpm clear
.github/scripts/markdownlint.sh
.github/scripts/file_names.sh
.github/scripts/sidebar.sh
.github/scripts/spelling.sh
pnpm build

[errose28]

Hi @will-sh thanks for adding this. Let's check with the Chinese speaking community if they are willing to maintain translations for all the documentation, or they would rather just use the English version since some things are difficult to translate and it's common for the translated docs to become out of date. @ChenSammi can you bring this up in the next APAC community sync?

[will-sh]

Thanks for the review @errose28. That's true. Multi-language support for just the site framework is easy enough, but translating every blog post would need a lot of effort to maintain.

[ChenSammi]

Hi @will-sh thanks for adding this. Let's check with the Chinese speaking community if they are willing to maintain translations for all the documentation, or they would rather just use the English version since some things are difficult to translate and it's common for the translated docs to become out of date. @ChenSammi can you bring this up in the next APAC community sync?

@errose28 no problem, will discuss this in next meeting.