refactor: better error handling 👍

[habibalkhabbaz]

Description

After reading the bot logs using docker logs binance-bot -f --tail 100, I see that the bot still has unhandled promise rejection warnings from redlock which may cause the bot to crash or restart the WebSocket.

These warnings lead me to do some research, and I found that if any error is thrown inside callback function, setInterval or setTimeout will be ignored by the parent try/catch. One solution is to use try/catch inside each block which is hard to do this everywhere. So that's what this pull request is going to solve.

I managed to solve this by implementing a global error handler using process to handle errors that are not caught by the bot.
I know that may catch any unexpected error but this will give us the benefit of handling and debugging any error easily.

Also, this may help us to report any error to any service such as "Sentry" in the future if planned.

Finally,
I don't mind if you do any changes to this pull request.
Any change will be welcomed. Or even if you have a better idea.

How Has This Been Tested?

It was tested locally and test files were also provided

[chrisleekr]

@habibalkhabbaz

This is looking really good. 👍
The code looks good. Let me test and merge later.

[chrisleekr]

@habibalkhabbaz
Released!

Thanks for the really good code!

[habibalkhabbaz]

Ohh, that was fast. Thank you for merging @chrisleekr
In fact, it was your idea and I just tried to refactor it.
Thanks again and happy trading!