fix(cli): provider i18n usage

[zettca]

• reverts fix(cli): remove redundant HvProvider #5055 (it wasn't an HvProvider 🤦)
• update docs URLs
• remove/comment supportedLngs to reduce maintenance effort of adding a new language

[Copilot]

Pull request overview

Reintroduces the app-shell Vite baseline’s i18n provider wiring (reverting the prior “remove redundant provider” change) and updates the i18n initialization code used by the CLI-generated template.

Changes:

• Wrap withProvider HOC output with the local Provider so react-i18next hooks have an I18nextProvider in scope.
• Simplify i18n instance initialization and memoization logic, and adjust inline documentation URL.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
packages/cli/src/baselines/app-shell/vite/src/providers/Provider.tsx	Restores wrapping of generated pages/components with the i18n Provider via the withProvider HOC.
packages/cli/src/baselines/app-shell/vite/src/lib/i18n.ts	Refactors i18n instance creation/config and changes memoization pattern for the template’s i18n singleton.

[Copilot]

i18next is using LanguageDetector, but the template only ships public/locales/en/.... Without load: "languageOnly" and/or supportedLngs: ["en"], locales like en-US will trigger backend requests for /locales/en-US/... that don't exist (404/extra round-trips) before falling back to en. Consider restoring load: "languageOnly" (and/or restricting supportedLngs) to match the baseline locale folder structure.

Suggested change

	fallbackLng: "en",
	fallbackLng: "en",
	load: "languageOnly",
	supportedLngs: ["en"],