Excessive error logging for parsing issues

[GriffinRichards]

Some parsing errors result in multiple logs that don't add new information. Example for trying to open wild encounters if the file is missing:

<timestamp> [ERROR] Could not open '<path>/wild_encounters.json': No such file or directory
<timestamp> [ERROR] Error: Failed to parse json file <path>/wild_encounters.json: unexpected end of input
<timestamp>  [WARN] Failed to read wild encounters from <path>/wild_encounters.json

ParseUtil should probably expose error messages to the caller and allow them to handle the details. The example above should look something like:

<timestamp>  [WARN] Failed to read wild encounters from '<path>/wild_encounters.json': No such file or directory