fix[frontend](integrations): added gcp missing translation keys

[AlexSanchez-bit]

No description provided.

[github-actions]

🛑 AI review — High/critical findings

One or more high/critical issues were found. Please review and fix before merging if they're real.

✅ architecture (gemini-3-flash-lite) — clean

Summary: Routine localization key update; no architectural or contract changes detected.

No findings.

🛑 bugs (gemini-3-flash-lite) — high/critical — please review

Summary: Renaming 'topic' to 'topicId' in localization files breaks existing UI lookups if the code still expects the 'topic' key.

• high frontend/src/shared/i18n/locales/de.json:2924 — Renaming 'topic' to 'topicId' will cause a missing translation error in the UI if the frontend code still references the 'topic' key.
• high frontend/src/shared/i18n/locales/es.json:2924 — Renaming 'topic' to 'topicId' will cause a missing translation error in the UI if the frontend code still references the 'topic' key.
• high frontend/src/shared/i18n/locales/fr.json:2924 — Renaming 'topic' to 'topicId' will cause a missing translation error in the UI if the frontend code still references the 'topic' key.
• high frontend/src/shared/i18n/locales/it.json:2924 — Renaming 'topic' to 'topicId' will cause a missing translation error in the UI if the frontend code still references the 'topic' key.
• high frontend/src/shared/i18n/locales/pt.json:2924 — Renaming 'topic' to 'topicId' will cause a missing translation error in the UI if the frontend code still references the 'topic' key.
• high frontend/src/shared/i18n/locales/ru.json:2824 — Renaming 'topic' to 'topicId' will cause a missing translation error in the UI if the frontend code still references the 'topic' key.

✅ security (gemini-3-flash-lite) — clean

Summary: Routine localization updates; no security vulnerabilities or information disclosure identified.

No findings.

🟢 go-deps — up to date

No pending Go dependency updates.

[AlexSanchez-bit]

frontend references topicId