[BUG] fix type of payload in MessageExample

[Pakisan]

Describe the bug.

Wrong definition of payload property

spec-json-schemas/definitions/3.0.0/messageExampleObject.json

Lines 25 to 31 in 2da0459

	"headers": {
	"type": "object",
	"description": "Example of the application headers. It can be of any type."
	},
	"payload": {
	"description": "Example of the message payload. It can be of any type."
	}

Expected behavior

MessageExample.payload must be defined as any type

{
    "headers": {
      "type":  "object",
      "description": "Example of the application headers. It can be of any type."
    },
    "payload": {
      "description": "Example of the message payload. It can be of any type."
    }
}

See:

• fix: parse message payload of any type other than map of String to Object jasyncapi#208
• [Docs Bug 🐞 report]: wrong type of payload in MessageExample website#3530

👀 Have you checked for similar open issues?

• I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to work on this issue ?

Yes I am willing to submit a PR!

[asyncapi-bot]

🎉 This issue has been resolved in version 6.8.1 🎉

The release is available on:

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

Your semantic-release bot 📦🚀