Update spec coverage for form pages in the Health Care Application

[longmd]

Are you removing, renaming or moving a folder in this PR?

• No, I'm not changing any folders (skip to TeamSites and delete the rest of this section)
• Yes, I'm removing, renaming or moving a folder

Did you change site-wide styles, platform utilities or other infrastructure?

• No
• Yes, and I used the proxy-rewrite steps to test the injected header scenario

Summary

This PR isolates updates spec coverage for various form pages, fields and review components. No updates were made to the methods themselves, just the spec coverage.

Related issue(s)

department-of-veterans-affairs/va.gov-team#60897

Acceptance criteria

• Spec coverage meets or exceeds allowable coverage numbers

Quality Assurance & Testing

• I fixed|updated|added unit tests and integration tests for each feature (if applicable).
• No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
• Linting warnings have been addressed
• Screenshot of the developed feature is added

Error Handling

• Browser console contains no warnings or errors.
• Events are being sent to the appropriate logging solution

[va-vfs-bot]

ESLint is disabled

vets-website uses ESLint to help enforce code quality. In most situations we would like ESLint to remain enabled.

What you can do

See if the code can be refactored to avoid disabling ESLint, or wait for a VSP review.

[coope93]

One small comment but looks great! Nice work on these. I'm really liking the subject pattern in these specs; it makes it way more readable to me.