feat(multi format schema): support new media types

[Pakisan]

• application/raml+yaml;version=1.0
• application/vnd.google.protobuf;version=2
• application/vnd.google.protobuf;version=3
• application/xml

Closes asyncapi/jasyncapi#214

Let's left them like ref, string or object. Generally idk which schema will represent them correctly

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[derberg]

do we need it here? in the end, it works without it listed here right? in the spec xml is not listed in the list of recommeneded schemas - and also, it is anyway just recommended

[Pakisan]

Yep, otherwise here will be error

asyncapi: 3.0.0
info:
  title: Account Service
  version: 1.0.0
  description: This service is in charge of processing user signups
channels:
  userSignedUp:
    address: user/signedup
    messages:
      UserSignedUp:
        $ref: '#/components/messages/userSignedUp'
operations:
  sendUserSignedUp:
    action: send
    channel:
      $ref: '#/channels/userSignedUp'
    messages:
      - $ref: '#/channels/userSignedUp/messages/UserSignedUp'
components:
  messages:
    userSignedUp:
      payload:
        schemaFormat: application/xml
        schema: |
          <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified">
            <xs:element name="User">
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="displayName" type="xs:string">
                      <xs:annotation>
                        <xs:documentation>Name of the user</xs:documentation>
                      </xs:annotation>
                  </xs:element>
                  <xs:element name="email" type="xs:string">
                      <xs:annotation>
                        <xs:documentation>Email of the user</xs:documentation>
                      </xs:annotation>
                  </xs:element>
                </xs:sequence>
              </xs:complexType>
            </xs:element>
          </xs:schema>

[Pakisan]

it is anyway just recommended

Yep, it's recommendation. But folks from Specmatic already have scenarios where they are using .xsd as payload schema

Without proper registration UI component will not work because of error in our parser

Error thrown during AsyncAPI document parsing. Name: Error, message: Unknown schema format

[Pakisan]

I have already checked this changes

Here are tests
https://github.com/Pakisan/asyncapi-developer-portal/blob/5d0deb2a734db84a8112e072c631a855883eb7a9/tests/multiFormatSchema.test.json#L4375-L4384