Story

As a user of RHDH,
I want the strings I configure in app-config.yaml (like app title, description, section names, etc.) to support translation,
so that I can provide a localized experience for different teams or regions without modifying source code.

Background

Currently, user-entered values in app-config.yaml are treated as plain text and displayed as-is. For example:

app:
  title: Developer Hub  

This prevents localization when an organization serves multiple audiences with different languages.

To support translations:

• Allow keys like titleKey or descriptionKey alongside user-entered strings.
• If a key is provided, translations are applied via translationApi.
• If translation is missing, fallback to the provided string.
• If no key is provided, default behavior remains unchanged (backward compatibility).

Acceptance Criteria

• app-config.yaml supports both plain strings and translation keys.
• If a translation key is provided, localized string is displayed.
• If translation is missing, fallback to user-entered string.
• If only a plain string is provided, behavior remains unchanged.