feat: init rsc support for translation

[tomerqodo]

Benchmark PR from qodo-benchmark#169

[sentry]

Bug: The Settings page is a Server Component but incorrectly calls the useTranslation() hook, which is only allowed in Client Components and will cause a runtime error.
_{Severity: CRITICAL}

Suggested Fix

Add the 'use client' directive to the top of the Settings page file (page.tsx). This will correctly designate it as a Client Component, allowing it to use hooks like useTranslation() as intended.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: web/app/components/plugins/marketplace/description/index.tsx#L3-L8

Potential issue: The Settings page component, located at
`web/app/(commonLayout)/datasets/(datasetDetailLayout)/[datasetId]/settings/page.tsx`,
is a Next.js Server Component as it lacks a `'use client'` directive. However, the code
directly calls the `useTranslation()` hook within this component. This is a violation of
a fundamental React rule that prohibits the use of hooks inside Server Components. This
will cause a runtime error when a user attempts to access the settings page, making it
non-functional.

_{Did we get this right? 👍 / 👎 to inform future reviews.}