fix(syntaxHighlighter): request and response examples for json cases

[tim-lai]

• OAS 2 request and response examples
• OAS 3 request and response examples

Description

• Check for json content across OAS2 and OAS3 request and response examples. If json, apply known "json" language to (syntax highlighter) HighlightCode props.
• New utils helper, jsonParse.js. Helps with try/catch boilerplate with use of JSON.parse()

Motivation and Context

Extends Fixes #6508

If json language is not provided, react-syntax-highlighter may try to escape certain character and/or long strings into multiple string segments. This results in unexpected multi-color render within the desired string.

How Has This Been Tested?

New Cypress tests with OAS2 and OAS3 samples. Note, the fail case would be instead of a single string within a single <span>, a broken example would have the string broken up into segments, each contained within its own <span>

Screenshots (if appropriate):

Checklist

My PR contains...

• No code changes (src/ is unmodified: changes to documentation, CI, metadata, etc.)
• Dependency changes (any modification to dependencies in package.json)
• Bug fixes (non-breaking change which fixes an issue)
• Improvements (misc. changes to existing features)
• Features (non-breaking change which adds functionality)

My changes...

• are breaking changes to a public API (config options, System API, major UI change, etc).
• are breaking changes to a private API (Redux, component props, utility functions, etc.).
• are breaking changes to a developer API (npm script behavior changes, new dev system dependencies, etc).
• are not breaking changes.

Documentation

• My changes do not require a change to the project documentation.
• My changes require a change to the project documentation.
• If yes to above: I have updated the documentation accordingly.

Automated tests

• My changes can not or do not need to be tested.
• My changes can and should be tested by unit and/or integration tests.
• If yes to above: I have added tests to cover my changes.
• If yes to above: I have taken care to cover edge cases in my tests.
• All new and existing tests passed.