Unfriendly handling of unhandled exceptions/rejections
My plug-in (homebridge-nest) unfortunately had a bug which led to an unhandled promise rejection in the case of a network error under specific circumstances. Shame on me! Fortunately I have now fixed it.

Unfortunately, Homebridge made this a little hard for me to debug (and my users to help me). It installs a default unhandled promise rejection handler which simply immediately quits, without showing any indication of where the unhandled rejection occurred, what caused it, etc. So my users just see Homebridge SIGTERM with no error. This makes things almost impossible to debug 'in the field'. Example:

```
[02/05/2022, 18:29:34] Error: read ECONNRESET
    at TLSWrap.onStreamRead (node:internal/stream_base_commons:220:20)
[02/05/2022, 18:29:34] [Nest] Retrying in 10 seconds.
**[02/05/2022, 18:29:34] Got SIGTERM, shutting down Homebridge...**
```

Can we make it more friendly? My recommendation: remove the handler completely. Modern versions of node already quit when there are unhandled promise rejections, so if you are going to quit, node does that already - and unlike Homebridge's 'minimal bomb' handler which says nothing, node prints useful info/stack trace which can help plug-in developers if this happens to end users.