Add logLevel=sql

That is good idea, I created to track it. 

I’m currently working on a large refactoring of the SQL processing and execution logic which should include better tracking and logging of SQL executed, but hadn’t gotten to the point of determine the best way to expose it back out. The logLevel=SQL approach may work well.



I would like to be able to run liquibase commands with --logLevel=sql. I would like it to display every SQL it runs (like in updateSQL)

At the moment I can only achieve this by running liquibase updateSQL update, because --logLevel=info doesn’t print enough and debug prints way too much things.