Update CTA widget code to use more modern pattern

[jilladams]

Status: [2024-06-18] Note from Jill in this Slack thread: this is Public Websites tech debt. Not timing critical, but did make a dumpster fire of testing Fri / yesterday. If Dave takes the CTA widget with him to the Health apps crew, this'll be a no op for us.

Context

As a result of moving CTA widget code to LH V1 / facilities-api V2, we found that our older code patterns made testing very difficult. We should update the code to future-proof testing.

Context:

• https://dsva.slack.com/archives/C076XFT3VCN/p1718739848738509
• https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/pull/1725/files

Issue to resolve

To test better in Staging, we could rewrite the CTA widget component to a function component that uses useEffect to only render after the props are received from the flipper vets-api endpoint.

Product pre-requisites / CHANGE MANAGEMENT

The CTA Widget is used all over the place by many teams in implementations we do not own. We need to understand:

• How would this change affect other users of the CTA widget?
• Do other teams need lead time to account for this change?

Acceptance Criteria

• [ ] Product has an understanding of CTA widget usage across OCTODE teams
  • [ ] Use cases are gathered
  • [ ] Timeline is established for prep / rollout, if appropriate
• [ ] CTA widget code reliably executes after flipper vets-api endpoint props are received, in Staging

[FranECross]

@jilladams Will this ticket be moving to another team, as many of the other widget tickets? Thanks!

[jilladams]

Maybe! Moving to the "transfer" column until that convo is resolved. Tracking ownership question in 2 places:

• Product sync board: https://dsva.slack.com/lists/T03FECE8V/F07BVDGCY8H?record_id=Rec07G6V7LUJZ
• Scrum topics board: https://dsva.slack.com/lists/T03FECE8V/F079GFKN50D?record_id=Rec07A9MB02SW