[BUG] Implement avro schema data type

[akkshitgupta]

Currently, the Avro Schema Input Processor does not handle the map, fixed and byte datatypes. This issue is a continuation of the work done in pull request #1753

Now, we need to add/implement:

• Dictionary Model for map data type as suggested in feat: add Avro Schema input processor #1753 (comment) conversation
• String Model for fixed and byte data type: need to update the toStringModel function in https:/asyncapi/modelina/pull/1753/files#diff-7172970fb3505bd86705eca0c2ef14740d102e6f4e828f18bedc431ba2097241
• unit tests for the added data types
• changes in docs/usage.md covering edge cases and other related things.
• a work-around to differentiate Avro Schema from JSON Schema - feat: add Avro Schema input processor #1753 (comment)

[github-actions]

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️