[10-10EZ] Add field keys for 10-10EZ pdf fill functionality

[coope93]

Summary

• This work is behind a feature toggle (flipper): NO, but it is not being called anywhere yet
• Add key mapping for vets-json-schema to 10-10EZ pdf file to be used to fill out pdf from form data.
• This PR is part 1 to just add the key mapping. A future PR will have some updates to ensure the correct values are displayed in the filled out pdf.
• 1010 Health Apps

Related issue(s)

• [BE] 10-10EZ - Print/save PDF: Map remaining fields and generate PDF va.gov-team#102888

Testing done

• New code is covered by unit tests
• Describe what the old behavior was prior to the change
• Describe the steps required to verify your changes are working as expected. Exclusively stating 'Specs run' is NOT acceptable as appropriate testing
• If this work is behind a flipper:
  • Tests need to be written for both the flipper on and flipper off scenarios. Docs.
  • What is the testing plan for rolling out the feature?

Screenshots

Note: Optional

What areas of the site does it impact?

10-10EZ, pdf filling

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

[coope93]

These are tested in the va1010ez_spec.rb file by confirming the generated pdf (simple.pdf) has the correct values filled out. I broke this out into it's own PR to make the diff smaller. These keys align with the vets-json-schema and the 10-10EZ pdf fields.

[github-actions]

1 Warning

⚠️

This PR changes 291 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/pdf_fill/forms/va1010ez.rb (+291/-0) Note: We exclude files matching the following when considering PR size: *.csv, *.json, *.tsv, *.txt, *.md, 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, *.pdf Big PRs are difficult to review, often become stale, and cause delays.

Generated by 🚫 Danger

[JoshingYou1]

LGTM! Nice work Brandon! 😄