[department-of-veterans-affairs/va-virtual-agent#951] Setup flipper for JWT fetching in the front end

[aaronyoung-tw]

Co-authored-by: Alex Person alex.person@thoughtworks.com

Note: Delete the description statements, complete each step. None are optional, but can be justified as to why they cannot be completed as written. Provide known gaps to testing that may raise the risk of merging to production.

Summary

1. Create a new flipper with end date May 2024
2. Add Aaron & Alex as flipper admins

cross referencing this pr from vets-website
Working from the virtual agent team

Related issue(s)

department-of-veterans-affairs/va-virtual-agent#951

• department-of-veterans-affairs/va.gov-team#0000
• Link to ticket created in va.gov-team repo
• Link to previous change of the code/bug (if applicable)
• Link to epic if not included in ticket

Acceptance criteria

• I fixed|updated|added unit tests and integration tests for each feature (if applicable).
• No error nor warning in the console.
• Events are being sent to the appropriate logging solution
• Documentation has been updated (link to documentation)
• No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
• Feature/bug has a monitor built into Datadog or Grafana (if applicable)
• If app impacted requires authentication, did you login to a local build and verify all authenticated routes work as expected
• I added a screenshot of the developed feature