User Story: Station Bot verification role-name configuration

[GitAddRemote]

User Story

As a guild owner or guild admin, I need to manage the Station-Bot verification role names so that the verified, temporary-member, and potential-applicant roles created or maintained in Discord match my guild’s terminology.

Definition of Done

• Station exposes editable controls for verifiedRoleName, tempMemberRoleName, and potentialApplicantRoleName
• Required-field validation and save/reload flows are covered by tests
• pnpm typecheck passes

Acceptance Criteria

• A guild admin can update the three verification role names from Station
• The saved values persist on reload
• Invalid values are rejected with field-level feedback instead of a generic failure

Technical Elaboration

This ticket covers the role-name portion of verification config from Station-Bot guild config. It is intentionally separate from verification enablement and org-member role mapping so implementation can stay small.

Design Elaboration

These inputs should use plain-language helper text because they map directly to visible Discord concepts. The UI should optimize for clarity over density.

---

Parent Epic: #231
Depends on: #232, #233, #242