Create proper diagnostics for JSON Errors

[Morxemplum]

As of now, there are diagnostics for Lua. Whenever a pack developer makes a mistake in Lua code and they try and run their code, usually the console can catch most of these errors and report back to the Pack Developer what they did wrong. This means the Pack Developer can go and fix that bug.

However, there are no official diagnostics for JSON (or it's poorly made). When a JSON error happens, the game crashes. New pack developers have a hard time knowing what JSON errors are, where they are, and how to fix them. This is something that previously may have stopped pack developers from making packs for Open Hexagon.

What to do? Whenever there is faulty JSON logic (non-existent IDs, incorrect file paths, or incorrect syntax), the game should refuse to load the level associated with that bad JSON file, and when Open Hexagon finishes loading, the console should report how many JSON errors there were (if there were any) and list them out so pack developers can understand what they did wrong and go to fix them. This must be done to make debugging easier for new and experienced pack developers alike.