[V1 & 3 Components] Implement available components for Find a Form

[FranECross]

Description

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.

Pages:

• Find a Form
• Forms results page
• Form Detail pages:
  • Example page
  • Another example

Elements that are not using components that should be

1. Link
   • We use this in one place but should be using the v1 component everywhere we can, including content inside inside accordions
   • We should also be using the appropriate variant (mainly download) for each instance
2. Action Link
   • On the results list, there are a couple links that look like they should be using secondary action links but it's not. We are using an icon instead of the proper VADS class

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 within VA.gov

Engineering notes / background

Analytics considerations

Quality / testing notes

Acceptance criteria

• Links are using V1
• Action Link the proper VADS class
• other features display correctly
• verify/review the E2E tests
• check desktop and mobile
• a11y review

[FranECross]

If breadcrumbs ISN'T content build, and is vets website, please add back to the ticket.

[randimays]

Discovered more changes that need to be made in content-build. I'm working on these changes now, so this will carry over, but hopefully close tomorrow or Thursday.

[randimays]

Successfully validated in production. Closing!