fix: add semantic roles to list and menu controls [WPB-14783]

[Garzas]

https://wearezeta.atlassian.net/browse/WPB-14783

---

PR Submission Checklist for internal contributors

• The PR Title

  • conforms to the style of semantic commits messages¹ supported in Wire's Github Workflow²
  • contains a reference JIRA issue number like SQPIT-764
  • answers the question: If merged, this PR will: ... ³

• The PR Description

  • is free of optional paragraphs and you have filled the relevant parts to the best of your ability

---

What's new in this PR?

Issues

• Controls in list rows, menu rows, and selectable rows did not always expose a semantic role to accessibility services.
• Some content descriptions included role words like “button”, which could cause duplicate TalkBack announcements once semantic roles are provided.

Causes (Optional)

• Shared clickable row components used clickable semantics without an explicit role.
• A couple of accessibility strings encoded the control role in user-facing text instead of relying on platform semantics.

Solutions

• Added explicit semantic roles to shared clickable list/menu row components.
• Added explicit RadioButton roles only at selectable row call sites that actually render radio buttons.
• Removed role words from affected content descriptions across localized resources.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud