fix(editor-preview): reset error boundaries on editor content change

[char0n]

When following AsyncAPI definition was provided to the editor, the AsyncAPI renderer crashed, error boundary caught the error and displayed the fallback component. When we changed the editor content to fix the issue, the fallback component was still displaying, because it's error state was persistent. This is fine in SwaggerUI content, where the definition is immutable. But it's impractical in SwaggerEditor@5 content, where definition always changes. This PR introduces override for error boundary mechanism provided by SwaggerUI, which detects if editor has changed. If the editor content has changed the error boundary state resets.

Definition:

asyncapi: '2.6.0'
info:
  title: AsyncAPI
  version: '1.0.0'
channels:
  'foo':
    description: Bar.
    publish:
      message:
        oneOf:
          - $ref: '#/components/messages/Foo'
       
          
components:
  messages:
    Foo:
      name: Foo
      payload:
        $ref: "#/components/schemas/Bar"
      examples:
        - name: standard
          payload:
            after: 
              oneOf:
              - $ref: '#/components/messages/Foo'
              
  schemas:
    Bar:
      type: object
      properties:
        eventType:
          type: string
          desciption: Foo

Fallback component displayed instead of rendered AsyncAPI definition:

[swagger-bot]

🎉 This PR is included in version 5.0.0-alpha.74 🎉

The release is available on:

• npm package (@alpha dist-tag)
• GitHub release

Your semantic-release bot 📦🚀