Refactor logger component

[howjmay]

logrus is under maintenance mode which means it is lack of some necessary feature (e.g. stack trace).

Moreover, it would be better to using error object serves as the error description instead of creating error sturct served for different purposes.

The logger library, zap is a library developed by uber can meet the needs I mentioned above. It would be great to introduce it in this project.

[howjmay]

embedding error object in zap would look like the following style

logger.Fatal("logging message", zap.Error(err))

[howjmay]

Refer this for implementing contextLogger with logrus
https://notes.burke.libbey.me/context-and-logging/