I18n translation

[Lantum-Brendan]

This PR handles a slight setup documentation modification and handles translation to locale languages.

2026-03-04.14-53-11.mp4

[sourceant]

Code Review Summary

This PR implements Internationalization (i18n) across the dashboard. It introduces translation files for multiple languages (EN, FR, DE, ES, PT, IT) and updates UI components to use the useI18n hook. It also refines some API URL configurations in the documentation.

🚀 Key Improvements

• Full i18n coverage for all primary views and components.
• Added a robust LanguageSelector component with flag icons.
• Updated README documentation to prevent common API URL configuration errors.
• Added comprehensive vitest.setup.ts to support i18n in unit tests.

💡 Minor Suggestions

• Deduplicate token normalization helper functions across views.
• Use translation keys for error strings in the Auth store.

🚨 Critical Issues

• Broken unit test in BackupsTab.test.ts due to case sensitivity mismatch in status badges.

[sourceant]

Review complete. See the overview comment for a summary.

[sourceant]

The error message 'API key is required' is still hardcoded while the rest of the app has been internationalized. This should use the $t function or be handled in the view layer with a translation key.

Suggested change

	if (!normalizedApiKey) {
	if (!normalizedApiKey) {
	error.value = "auth.errors.apiKeyRequired";
	loading.value = false;
	return false;
	}

[sourceant]

When calling templatesApi.refresh(), the response potentially contains a count or message that is being ignored in favor of a static notification. It's better to verify if the count needs to be passed to the translation string.

Suggested change

	try {
	const response = await templatesApi.refresh();
	notifications.success(
	t("settings.general.quickActions.templatesRefreshedTitle"),
	t("settings.general.quickActions.templatesRefreshedDesc", { n: response.data.count || 0 })
	);