Sketch: e2e rspec tests

[jeffcatania-usds]

Ticket

Resolves FFS-2687

TODOS

• switching the driver to selenium_chrome_headless changed the nature of the puffing billy mocks required to simulate moving through the flow. That will require tweaking so it passes locally and in rspec CI.
• the help specs need to be rewritten in the VCR/puffing billy format so they can pass as well.
• the remainder of the e2e flow for pinwheel needs to be fleshed out (generating a pdf, simulating webhooks for all events)
• for the simulation of webhooks, there might be a way to fake encrypt the message so it can be decrypted by the webhooks controller. at worst case, refactoring so the simulation doesn't drift would be desirable.
• once the flow is fleshed out for pinwheel, a followup story to do the same for argyle also should happen.

Changes

Context for reviewers

To re-record mocks, flip RECORD_OPTION in app/spec/e2e/cbv_flow_spec.rb to "all" if you need to record a new interaction
to run these tests with record: :all, make sure you have a .env.test.local with PINWHEEL_API_TOKEN_SANDBOX, then you can run this test via running
to run these tests at all, explicitly via rubymine, or RUN_E2E_TESTS=1 bundle exec rspec spec/e2e/cbb_flow_spec.rb.

Acceptance testing

• No acceptance testing needed
  • This change will not affect the user experience (bugfix, dependency updates, etc.)
• Acceptance testing prior to merge
  • This change can be verified visually via screenshots attached below or by sending a link to a local development environment to the acceptance tester
  • Acceptance testing should be done by design for visual changes, product for behavior/logic changes, or both for changes that impact both.
• Acceptance testing after merge
  • This change is hard to test locally, so we'll test it in the demo environment (deployed automatically after merge.)
  • Make sure to notify the team once this PR is merged so we don't inadvertently deploy the unaccepted change to production. (e.g. :alert: Deploy block! @ffs-eng I just merged PR [#123] and will be doing acceptance testing in demo - please don't deploy until I'm finished!)

[iannorriscms]

Outstanding work left:

• switching the driver to selenium_chrome_headless changed the nature of the puffing billy mocks required to simulate moving through the flow. That will require tweaking so it passes locally and in rspec CI.
• the help specs need to be rewritten in the VCR/puffing billy format so they can pass as well.
• the remainder of the e2e flow for pinwheel needs to be fleshed out (generating a pdf, simulating webhooks for all events)
• for the simulation of webhooks, there might be a way to fake encrypt the message so it can be decrypted by the webhooks controller. at worst case, refactoring so the simulation doesn't drift would be desirable.
• once the flow is fleshed out for pinwheel, a followup story to do the same for argyle also should happen.