[DBEX] create UploadStatusUpdater PORO

[freeheeling]

Summary

Objective: Implements a system for periodically polling the Lighthouse uploads/status endpoint to confirm the status of supplemental documents submitted to Lighthouse as part of a Form 526 Submission. The purpose of this system is to surface successes and failures that happen in the Form 526 process after being forwarded to Lighthouse for processing.

• Create UploadStatusUpdater PORO
  • encapsulates parsing of complex nested response from Lighthouse Benefits Documents API 'uploads/status' endpoint
  • provides convenience methods for verifying whether a document has completed all processing, failed processing, or transitioned to another step in the process
• Subsequent PRs will further implement the interaction with the Lighthouse Benefits Document API client
• This work is behind a feature toggle (flipper): YES/NO
• Responsible team: Disability Benefits Experience Team 2 (dBeX Carbs 🥖)

Related issue(s)

• [DBEX] create Lighthouse526DocumentUpload migration #17405
• [DBEX] create Lighthouse526DocumentUpload model with state #17407
• Form 526 Document Upload - Lighthouse status polling system #15964
• [Doc Upload Polling] Finish PR for Implementation va.gov-team#87621
• [Doc Upload Polling] Implement Model In Separate PR va.gov-team#87619
• [Epic] Implement Document Upload Polling Solution va.gov-team#75804

Testing done

• New code is covered by unit tests

What areas of the site does it impact?

• non-user facing, asynchronous job tracking the status of uploaded documents submitted in conjunction with Form 526EZ

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 (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

[github-actions]

1 Warning

⚠️

This PR changes 283 LoC (not counting whitespace/newlines). In order to ensure each PR receives the proper attention it deserves, we recommend not exceeding 200. Expect some delays getting reviews. File Summary Files lib/lighthouse/benefits_documents/form526/upload_status_updater.rb (+118/-0) spec/lib/lighthouse/benefits_documents/form526/upload_status_updater_spec.rb (+165/-0) Note: We exclude files matching the following when considering PR size: *.csv, *.json, *.tsv, *.txt, Gemfile.lock, app/swagger, modules/mobile/docs, spec/fixtures/, spec/support/vcr_cassettes/, modules/mobile/spec/support/vcr_cassettes/, db/seeds, modules/vaos/app/docs, modules/meb_api/app/docs, modules/appeals_api/app/swagger/, *.bru Big PRs are difficult to review, often become stale, and cause delays.

Generated by 🚫 Danger