fix: internationalize PayPal Setup component

[veeceey]

Noticed the PayPal Setup component had a bunch of hardcoded English strings with a @TODO: translate comment sitting there. Went through and replaced all of them with t() calls.

What changed:

• Form labels ("Client Id", "Secret Key") now use existing locale keys (client_id, secret_key)
• All headings, paragraphs, list items, and the setup instructions are now wrapped in t()
• Added ~15 new translation keys to en/common.json for the PayPal-specific strings
• Removed the @TODO: translate comment since it's done now
• Reused existing keys where they already existed (save, here, keys_have_been_saved, client_id, reminder)

Testing:

• Verified the component renders the same English text as before (just through the i18n layer now)
• No functional changes, purely i18n wrapping

Fixes #27907

[CLAassistant]

All committers have signed the CLA.

[cubic-dev-ai]

1 issue found across 2 files

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="apps/web/public/static/locales/en/common.json">

<violation number="1" location="apps/web/public/static/locales/en/common.json:4641">
P3: Duplicate "resources" key added; common.json already defines "resources" earlier in the file. Duplicate JSON keys are invalid and the later value overwrites the earlier entry.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[vetrivelanarsu]

Hey @veeceey, I noticed the bot flagged a duplicate resources key in common.json. Since this PR is still a draft and has failing checks, would u like me to help fix this or look for other untranslated strings in the component that might have been missed?

[veeceey]

Hey @vetrivelanarsu, thanks for the heads up! I already fixed the duplicate resources key in the latest commit (6b66060). I did a scan of the PayPal Setup component and I believe I've covered all the hardcoded strings now — the remaining text in the component is dynamic (e.g., currency codes, PayPal-specific identifiers) rather than user-facing copy that needs translation. But if you spot anything I missed, definitely let me know!