[V1 & 3 Components] Implement available V1 or V3 components for Reusable Q&A with standalone page

[laflannery]

Background

The Design team is releasing a Typography update (sometime in March), which means that the PW team needs to upgrade any of our products where components aren't currently being using, but a V1 or V3 component is available.

If the updates aren't made prior to the Typography update, there's a chance that Veteran-facing issues may occur.

Example pages:

• Can I call VA to reset my Login.gov or ID.me password?
• What’s a Veteran Health ID Card (VHIC) and how do I get one?

Elements that are not using components that should be

1. Link
   • We should be using the v1 component everywhere we can, including content inside accordions and other components
2. Telephone
   • The component is not being used anywhere but should be, including inside accordions and other content

Possibly templated into all Resources & Support pages so may only need to be completed once

1. Radio buttons
   • There are rating radio buttons that should be using v3 component
2. Button
   • Submit button for the rating should use the v3 component
3. Telephone
   • Within this reused section, the V1 component should be added into the "Need more help?" section

Might be resolved with the Resources Landing page ticket but if not:

1. Search input
   • We should be using the v3
2. Radio buttons
   • There might be some technical limitations here, I'm not sure but if possible we should be using v3 components

From #17001

User story

AS A PO/PM for Public Websites products
I WANT to implement available V1 or V3 components in features & products currently under Public Websites management where components aren't currently being used
SO THAT all PW products are in alignment with the current component version
AND Veterans and other users have a consistent experience throughout VA.gov tools and information

Engineering notes / background

Analytics considerations

Quality / testing notes

Acceptance criteria

• Link is is using V1 components
• Telephone is using V1 components
• Radio buttons are using V3 components (if not templated in the Resources & Support pages as noted above)
• Button is using V3 components (if not templated in the Resources & Support pages as noted above)
• Telephone is using V3 components (if not templated in the Resources & Support pages as noted above)
• other features display correctly
• verify/review the E2E tests
• check desktop and mobile
• a11y review

[randimays]

The section below will be taken care of on #16986 & #17199. We can remove the search input and the search input's radio buttons from the requirements.

[laflannery]

@Randi @FranECross @jilladams I believe we can close this one too (as we did Step-by-step and FAQs) because everything remaining here is CMS content that we cannot convert to components

[FranECross]

Closing per Laura's comment above.