refactor: explicitly show error messages

[xayanide]

Description
Usually, when there are errors, IRC client error event triggers log4js, logs them like this:

[14:16:14.613][ERROR] irc - ERROR: {}

{} alone is not really helpful.
Like what was shown in issue #23

So, I added these 2 expressions as failsafes for this.

JSON.stringify(message.stack) for errors that needs to be converted into JSON like objects or values.

message.stack alone for errors that do not need to be converted into JSON.

Then be able to trace where the error had occured, not just the error message alone. In just a single template literal.

Also through this, the end user should be able to send informative error stacks in their issue's descriptions.

Example error:

[14:16:14.613][ERROR] irc - ERROR:
// JSON.stringify(message)
{} 
// JSON.stringify(message.stack)
"TypeError: Example is not a constructor\n    at Object.GetObject 
// long error stack here
(C:\\Users\\User\\Desktop\\osu-ahr\\dist\\cli\\index.js
// message
TypeError: Example is not a constructor
// message.stack
TypeError: Example is not a constructor
    // long error stack here
    at Object.GetObject (C:\Users\User\Desktop\osu-ahr\src\Example.js:0:0) 

If any, suggest changes on how can this be implemented better.