Standardize the Logging system for CLI with that of engine

[abhishekkumams]

standardize the error message output? Some error you are using Console.Error.WriteLine. Some you are using Console.WriteLine, which is going to stdout. Does not have to be in this PR but right now, it is very confusing.

Originally posted by @jarupatj in #800 (comment)

UPDATE:

We will use logger in CLI as well to be consistent with the Engine code and also it will have the below advantages:
The logger gives to ability to define different levels of importance of the logged messages and the ability to use different sink for the output - the console, a file, etc.

Also it's easy to enable or disable only some type of message when using a logger - for example you don't want to see every debug message in production.

[abhishekkumams]

CLI is mostly used as console application, where Informations are also important and should be displayed on the console always, such as the name of config file being picked up or certain warnings. By Default, logLevel is set to Error for Engine, which will skip Information and warning logs. So, for CLI we have to set default logLevel as Information unlike Engine. Setting to Information will also display any higher LogLevels.

[abhishekkumams]

TBH, while testing my changes I realized that this logging mechanism doesn't feel natural to CLI.

For example: it takes more screen and also it outputs the class name, which is irrelevant for developers.
I'm looking for some other loggers or customizing the ILogger to make it resemble more like other CLIs.