Overhaul metadata parsing

[Protonull]

No description provided.

[Protonull]

This PR refactors metadata.ts to rely on zod for config validation. The config files themselves are still manually read and parsed into JSON, but then that JSON is fed into a premade zod schema, eg:

// This is an actual snipped of code from the PR
const CONFIG_SCHEMA = z.object({
	host: z.string().default('0.0.0.0'),
	port: z.coerce.number().positive().max(65535).default(12312),
	gameAddress: z.string(),
	whitelist: z.boolean().default(true),
})

The only drawback, to exaggerate a little, is that zod's errors aren't particularly helpful for laymen. Even if someone isn't a programmer, the error that's thrown for a missing file is still fairly legible to many inexperienced users... whereas zod errors aren't. Even with the addition of zod-validation-error, a library specifically about pretty-printing zod errors to users, can be unhelpfully phrased. For example, using the example above, not including the required 'gameAddress' value produces the following error: Validation error: Required at "gameAddress"

[Huskydog9988]

Yea I'm mostly fine with that, I just want to know if there is a relatively easy way to add context that this error happened in the config file for example? I feel like we could reasonably diagnose the issue if someone approached us with this as is, but additional context would make it easier.

[Protonull]

I just want to know if there is a relatively easy way to add context that this error happened in the config file for example?

Yeah, the error gets prefixed with the file path here.