[FSR] Refactor resolution options radio button group to use design system component

[josephrlee]

Description

Enter a detailed description of the work - gherkin syntax below is acceptable.

Given: A veteran fills out the FSR When: They select a resolution option to resolve a debt Then: They should see a design system component instead of our custom component

Tasks

• [x] Use radio button component to replace the custom ResolutionOptions.jsx and update logic
• [x] Use the required label from the component and not our custom one that shows up randomly after the text
• [x] Fix the display of the really small text after an option is selected to match the design in Figma and get rid of the extra required labels

Design and Front End sync on implementation of design

• [X] Required
• [ ] Complete
• [ ] Not Required

Acceptance criteria

• [ ] Resolution options use the design system component
• [ ] Extra required labels have been removed
• [ ] Insoncistient type sizing has been fixed

Testing

• [ ] N/A if non development work
• [ ] Testing passed and documented in this ticket based off the "Then" statement in the description

Testing procedure: If additional testing steps or credentials to perform testing are needed list them here

---

Ticket creation

Ticket requirements

### Required to be "Ready" - [ ] Description written - [ ] Tasks defined - [ ] Acceptance criteria written - [ ] Testing defined - [ ] Add Labels - [ ] Attach to an Epic - [ ] Estimate Points

[josephrlee]

Hey team! Please add your planning poker estimate with Zenhub @Dr-Pongo @OptionSelect @amponce

Also, it won't look exactly like the Figma mockups because those have the minimal header pattern applied to them, but I'll work with y'all to make sure the styling is correct.

[OptionSelect]

Pulled in late to sprint 133