Rename frontend risk classification strings to risk assessment

Wanderson Policarporequested to merge
630589-rename-risk-classification-strings-frontend into master

What does this MR do and why?

The Product team decided to call the feature "Risk Assessment" instead of "Risk Classification". This MR is the frontend half of the split of !257357 (merged). It updates the 19 translatable strings in the merge request risk assessment widget, so their gettext namespace changes from RiskClassification| to RiskAssessment|. This MR depends on MR1 (!257357 (merged)) and targets its branch, so merge MR1 first.

References

Screenshots or screen recordings

No visual change is expected. The English text stays the same. Only the gettext namespace changes.

How to set up and validate locally

  1. In a Rails console, enable the flags: 
    Feature.enable(:duo_mr_risk_classification)
Feature.enable(:show_duo_mr_risk_classification_widget)
  2. Create a merge request in the gitlab-duo/test project.
  3. On the merge request page, confirm the risk assessment widget renders as before: for example, "Risk assessment pending", then the risk tier, confidence badge, rationale, and the "What contributed to this score" breakdown after the flow completes.
  4. Optional: to confirm the new namespace is in use, switch your user's preferred language to a language other than English. Confirm the widget strings fall back to English, with no raw RiskAssessment| prefix visible.

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports