Update vets-json-schema

[TaiWilkin]

Summary

• Now that Update the state labels and abbreviations for Canada. vets-json-schema#878 is in place for vets-json-schema to update the province codes, we are updating vets-api. Paired with Pensions - Update vets-json-schema vets-website#29178.

Related issue(s)

• Update vets-api lock file for vets-json-schema va.gov-team#80659
• Update the state labels and abbreviations for Canada. vets-json-schema#878
• Pensions - Update vets-json-schema vets-website#29178

Testing done

• Submitted form and confirmed updated addresses were accepted.

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

[TaiWilkin]

The schema id for form 40-10007 was updated by 15bda2f, due to the update to the common state enum for Canadian provinces.

[jperk51]

lgtm

[rmtolmach]

Is this right? I see 22.1.0 here: https://github.com/department-of-veterans-affairs/vets-json-schema/pull/878/files#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519

[TaiWilkin]

Yes, because vets-website has gotten updated to 22.1.0 since then (https://github.com/department-of-veterans-affairs/vets-website/blob/0ee8639c13d4da5c4520e70c2e79bb75236407c5/yarn.lock#L20599), so it seemed best to keep them in sync