VYE-226

[jsimonVA]

Summary

This PR is to update the JSON-Schema commit hash to align with JSON-SCHEMA repo updates. No other changes are in this PR

JSON-SCHEMA PR -> department-of-veterans-affairs/vets-json-schema#850

VETS-API PR -> As soon as this PR is approved and merge we will create the VETS-API PR with the new build pointing to the master hash commit of the updated JSON-SCHEMA
DRAFT PR that will be rebuilt once JSON-SCHEMA is in master -> https://github.com/department-of-veterans-affairs/vets-api/pull/15755/files

• (Summarize the changes that have been made to the platform)
• (If bug, how to reproduce)
• (What is the solution, why is this the solution)
• (Which team do you work for, does your team own the maintenance of this component?)
• (If using a flipper, what is the end date of the flipper being required/success criteria being targeted)

Related issue(s)

• Link to ticket created in va.gov-team repo
  department-of-veterans-affairs/va.gov-team#0000
• Link to previous change of the code/bug (if applicable)
  department-of-veterans-affairs/vets-website#0000
• Link to epic if not included in ticket
  department-of-veterans-affairs/va.gov-team#0000

Testing done

• Describe what the old behavior was prior to the change
• Describe the steps required to verify your changes are working as expected
• Describe the tests completed and the results
• _Exclusively stating 'Specs and automated tests passing' is NOT acceptable as appropriate testing
• Optionally, provide a link to your test plan and test execution records

Screenshots

Note: This field is mandatory for UI changes (non-component work should NOT have screenshots).

	Before	After
Mobile
Desktop

What areas of the site does it impact?

(Describe what parts of the site are impacted if code touched other areas)

Acceptance criteria

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
• Documentation has been updated (link to documentation *if necessary)
• Screenshot of the developed feature is added
• Accessibility testing has been performed

Error Handling

• Browser console contains no warnings or errors.
• Events are being sent to the appropriate logging solution
• Feature/bug has a monitor built into Datadog or Grafana (if applicable)

Authentication

• Did you login to a local build and verify all authenticated routes work as expected with a test user

⚠️ Team Sites (only applies to modifications made to the VA.gov header) ⚠️

• The vets-website header does not contain any web-components
• I used the proxy-rewrite steps to test the injected header scenario
• I reached out in the #sitewide-public-websites Slack channel for questions

Requested Feedback

(OPTIONAL) What should the reviewers know in addition to the above. Is there anything specific you wish the reviewer to assist with. Do you have any concerns with this PR, why?