Convert from Postman Collection 2.1 to AsyncAPI 3.0

[jonaslagoni]

This issue is part of a longer vision for the converter that can be found here: #221

It would be great to open up how easily people can switch or try out AsyncAPI based on existing resources. One of these is the Postman Collection, which defines a bunch of HTTP requests in a grouping called collections that contain items (requests) and folders.

I think we can combine this issue with #233, so when that functionality is solved, we can use postman2openapi or postman-to-openapi to first convert it to OpenAPI 3.0, and then use the existing converter to convert it to AsyncAPI.

NOTICE, because of the difficulty of this issue, you will be able to contact me all the time through Slack if you get stuck solving it at any point and even have calls when relevant.

[asyncapi-bot]

🎉 This issue has been resolved in version 1.6.0 🎉

The release is available on:

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

Your semantic-release bot 📦🚀

[aeworxet]

I would suggest researching the possibility to run @asyncapi/converter v1.6.0+ in a browser (maybe in a wrapper if that is not possible natively?) to avoid repeating situations like asyncapi/studio#1138.

@Amzani @KhudaDad414 @Shurtu-gal @Gmin2 @ItshMoh