Updating json-schema tag

[TaylorKrusen]

What/Why/How?

Updates the json-schema tag to reflect new format.

Reference

This change impacts downstream documentation.

Testing

Previewed change by updating the tag in locally running version of downstream docs.

Check yourself

• [ ] Code changed? - Tested with redoc/reference-docs/workflows (internal)
• [ ] All new/updated code is covered with tests
• [ ] New package installed? - Tested in different environments (browser/node)

Security

• [x] Security impact of change has been considered
• [x] Code follows company security practices and guidelines

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: 81f82afd7ac6b8379331f5d922ab6676de81dcc7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions[bot]]

Command	Mean [ms]	Min [ms]	Max [ms]	Relative
redocly lint packages/core/src/benchmark/benches/rebilly.yaml	971.2 ± 28.4	936.5	1029.0	1.02 ± 0.04
redocly-next lint packages/core/src/benchmark/benches/rebilly.yaml	954.0 ± 18.9	928.5	988.5	1.00

[github-actions[bot]]

Coverage report

St.:grey_question:	Category	Percentage	Covered / Total
🟡	Statements	77.02%	4452/5780
🟡	Branches	67.5%	2463/3649
🟡	Functions	70.64%	741/1049
🟡	Lines	77.22%	4187/5422

Test suite run success

734 tests passing in 102 suites.

Report generated by 🧪jest coverage report action from 81f82afd7ac6b8379331f5d922ab6676de81dcc7