doc: avoid mentioning 'uncaughtException'

I think we should not mention the 'uncaughtException' event in the documentation of the error events. Experience has taught me that it is usually used in the wrong way leading to bizarre situations like parsers blocked in a wrong state, events emitted multiple times when they should not, etc. If an 'error' event does not have a listener the process should just exit.

Checklist

• documentation is changed or added
• commit message follows commit guidelines

Affected core subsystem(s)

doc