[Suggestion] Throw an error when JSON configs can't load instead of silent reversion to default configs

[pinkygrocket]

When Visuality's JSON configs cannot be parsed for whatever reason, the mod silently replaces them with default configs. This requires packdevs (myself included) to take extra steps to ensure that their configs aren't replaced when they're unaware- e.g. constant monitoring, frequent backups or commits, etc. which can be cumbersome. By contrast, mods such as CraftTweaker, KubeJS, InControl, and similar announce when their scripts or configs have failed parsing so that the packdev can fix them. This change would be a great quality-of-life feature for packdevs working with Visuality.