[#951] Refactor the Virtual Agent JWT fetch code to use a helper class.

[aaronyoung-tw]

Co-authored-by: Maurice Okumu maurice.okumu@thoughtworks.com

Summary

We refactored the Virtual Agent JWT fetch POC code to allow for the extending of the common::client::base

• (Which team do you work for, does your team own the maintainence of this component?)
  Virtual Agent Chatbot team

Related issue(s)

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

Testing done

Tested locally but we need to continue testing in staging - this feature is behind a flipper which won't make it to production. As before we didn't create a spec file as this will be a short-term POC (under a week) we intend on cleaning up.

• Describe what the old behavior was prior to the change
• Describe the steps required to verify your changes are working as expected
  Hit the endpoint with postman using the appropriate headers/cookies and getting a returned JWT
• Describe the tests completed and the results
  Getting a 403 from an endpoint as we are not behind the VA network to continue testing locally

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

[jeremy6d]

Did you mean to leave this in?

[aaronyoung-tw]

Removed this unintentionally commited file and also cleaned out other dead code

[ryan-mcneil]

👌