Fix: Remove path analysis from debug log (fixes #4631)

[ilyavolodin]

I didn't remove any of the logging, I just changed debug command to not include code-path logs. This way, people can still get path analysis logs by running DEBUG=eslint:*

[nzakas]

I don't think we want to just eliminate all code path messages. We should still have some basic logs coming from that module, just not so many.

[ilyavolodin]

Well, the logs are not eliminated, they are just removed from --debug flag. You can still access them by doing DEBUG=eslint:* from the command line. I looked through the path analysis logging and all we log is enter/leave code path. I don't see how this might help end-user debug an issue, this is only helpful for rule developers, and they still have work-around to get to the logs.
Problem with logging less is I could remove logging for enter/leave, and only leave DOT logs, but they are pretty massive even on their own, more then that, they are not human readable (since they are meant to generate graphs through graphviz. If I remove DOT logs, and leave enter/leave then every node in AST will be logged.

[nzakas]

Hmmmm ok. @mysticatea do you agree?

[mysticatea]

I'm OK.
I'm sorry about many logs.