Made dumpQueriesOnException = false by default as per documentation.

[King-hT]

…Added a unit test case for the same.

[King-hT]

This PR is raised based on 2 things.

1. Making the code in sync with documentation.
   
2. In our project, we value user data a lot. And there was a security bug reported by the team as the query had the critical user information logged in the stack trace.
   Now, this could be a common issue with others where they do not want the queries to be printed on the exception stack trace.
   For now, we have solved this by adding 'dumpQueriesOnException=false' to the host URL.

[vaintroub]

If you value security a lot, maybe you should not show the raw SQLException text?

[King-hT]

@vaintroub Thanks for the comment. I was wondering if I was missing any step as no one was even looking at my PR.

Well, you can say it as a bad design that we have in place or bad structure. But we have many classes which catch the exception and pass it ahead as our Business Exception which logs everything.
I get what you are saying, but in our case, it would be very difficult to catch SQLException everywhere and eat the exception trace.

That's where the dumpQueriesOnException comes into the picture. We have currently solved the issue by adding 'dumpQueriesOnException=false' to the host URL.

[rusher]

Thanks for contribution. this has been merged on develop branch, with additional commit c58c2ab for tests correction