suggestion: replace `YamlError` with native errors

[iuioiua]

          Should we split `YamlError` into `ParseError extends SyntaxError` and `StringifyError extends Error` like in csv?

Originally posted by @timreichen in #5328 (comment)

[timreichen]

On that topic: There are two standards now: Throwing native errors (msgpack, jsonc, ini, csv, encoding, semver), and custom errors (dotenv, toml, yaml).
Maybe we could have all std parse/stringify mods behave the same and therefore more predictably. Shall we get rid of TOMLError and YamlError completely and replace them with native errors?

[iuioiua]

Well, we throw custom errors in assert, async, csv, dotenv, fs, io, testing, toml and yaml. It's a good suggestion, but I'm on the fence. Can you please open an issue with the suggestion? It'd be good to hear other opinions. I've made this change for csv and toml.

[iuioiua]

I'm not yet certain that we should use native errors in all cases, but I think we should at least align with JSON.parse() and JSON.stringify() in their exceptions, for packages that parse and stringify. These exceptions are SyntaxError and TypeError, respectively.