fix: highlight code scroll console error (#7497)

[kristina-kovacikova]

Description

• fix for "Unable to preventDefault inside passive event listener due to target being treated as passive"
  • commonly advised solution => setting CSS property touch-action: none did not fix the issue
  • as a workaround for the error manual event listener for scroll has been added to componentDidMount to be able to set option {passive:false}

Motivation and Context

Fixes #7497

How Has This Been Tested?

• go to swagger-ui and run npm run dev wait a while and open localhost:3200
  • expand PUT /pets endpoint
  • click inspect on the example body
  • in dev tools - elements search for code element within div with class "highlight-code"
    • edit code element as HTML and duplicate it => as a result the example body will be longer and scrollable
    • now that the example body is scrollable open console in devtools and scroll example body all the way till the whole page starts scrolling => there should be no errors in the console

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.

[char0n]

@kristina-kovacikova thank you for the PR.

Can you please remove modified package-lock.json file from this PR? I assume the change was accidental.

[kristina-kovacikova]

@mathis-m tested and committed your suggestions, thanks

[char0n]

Great job! Thank you for contributing.

[char0n]

please build