[FEATURE] Please support *.json5 extension

[spyro2000]

Why do we need this improvement?

I love to use JSON5 instead of json because I can add comments. When I change the extension from "json" to "json5" the file is still recognized as AsyncAPI file, but the preview stops working, same for the validation

This also happens when there actually aren't any comments in the file.

How will this change help?

User could comment their files, having trailing commas etc.

Screenshots

No response

How could it be implemented/designed?

Internally convert JSON5 to JSON before processing it.

🚧 Breaking changes

No

👀 Have you checked for similar open issues?

• I checked and didn't find a similar issue

🏢 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to work on this issue?

None

[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.

[Pakisan]

@spyro2000 hi!

Does FasterXML works good with json5? If yes, I can try to add support for .json5 extension

It can be implemented with next limitations:

• https://stackoverflow.com/questions/68312227/can-the-jackson-parser-be-used-to-parse-json5
• JsonReadFeature: Introduce missing features for JSON5 compatibility FasterXML/jackson-core#707