feat(i18n): Translate Dashboard UI into Simplified Chinese

[pggdev]

Part of #243

Summary

Add i18next-based internationalization support for the Dashboard section and include English and Simplified Chinese translation resources.

Changes

• Added i18next setup with React integration
• Added browser language detection with localStorage persistence
• Added English and Simplified Chinese Dashboard translation keys
• Replaced Dashboard hardcoded text with i18n keys
• Translated Dashboard stats and errors
• Translated Job Status pie chart title, labels, and empty state
• Translated Queue Resources bar chart title, dropdown labels, axis labels, legend labels, and empty state

Scope

This PR only covers the Dashboard translations.

Manual verification can be done by setting i18nextLng in localStorage to en or zh-CN. A language switcher will be added in a follow-up PR to make this easier from the UI.

ScreenShots

Verification

• npm run lint -w frontend
• npm run test -w frontend -- --run
• npm run build -w frontend

[volcano-sh-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign william-wang for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[volcano-sh-bot]

Welcome @pggdev! It looks like this is your first PR to volcano-sh/dashboard 🎉

[gemini-code-assist]

Code Review

This pull request implements internationalization (i18n) for the Volcano Dashboard using react-i18next, introducing support for English and Chinese. Multiple components, including JobStatusPieChart, QueueResourcesBarChart, and the main Dashboard, were refactored to replace hardcoded strings with translation keys, and Dashboard.jsx was updated to wrap data fetching in useCallback. Feedback identifies an improvement opportunity in QueueResourcesBarChart.jsx to simplify the getResourceLabel function by utilizing the existing resourceTranslationKeys mapping instead of a redundant switch statement.

[gemini-code-assist]

The getResourceLabel function uses a switch statement that duplicates logic already present in the resourceTranslationKeys mapping. To improve maintainability and ensure consistency, you should use the mapping object instead of a switch statement.

    const getResourceLabel = (resource) => {
        const key = resourceTranslationKeys[resource];
        return key 
            ? t(`dashboard.charts.queueResources.resourceNames.${key}`) 
            : resource.toUpperCase();
    };