fix: make no argument passed validation opt-in

[IvoGoman]

#295 introduced stricter checking of query arguments. This results in new test failures when using e.g. ExpectedQuery or ExpectedExec without WithArgs(..) and the actual query passes arguments. This case of no expected arguments but actual arguments passed was previously not caught.

However, there is also the case where queries are matched via QueryMatcherRegexp and there is no intention to strictly validate the actual arguments. This case broke with the above mentioned change and requires rather cumbersome fixing as such:

// this would fail with arguments do not match: expected 0, but got 6 arguments
mock.ExpectExec("INSERT .*foobar::foobar.*").WillReturnResult(sqlmock.NewResult(0, 1))
...
// this would be the fix
mock.ExpectExec("INSERT .*foobar::foobar*").WithArgs(sqlmock.AnyArg(), sqlmock.AnyArg(), sqlmock.AnyArg(), sqlmock.AnyArg(), sqlmock.AnyArg(), sqlmock.AnyArg()).WillReturnResult(sqlmock.NewResult(0, 1))

In order to allow for both strict and relaxed matching of the expectations this change adds WithoutArgs(). This new Method on ExpectedQuery and ExpectedExec allows to strictly ensure that the actual query does not pass any arguments.
This reverts the strict argument checking introduced with #295 and makes this behavior opt-in.
Furthermore, a test will panic if both WithArgs(..) and WithoutArgs() are used together.

[IvoGoman]

@filikos @JessieAMorris could you kindly have a look at this PR?

[filikos]

Since the name noArgs is internal, lets adjust the error msg: The users should know right away if WithoutArgs()or WithArgs() is being used correctly: Lets adjust the error to something like: received arguments *all arguments key+value* but expected no arguments. Expect the query to be WithoutArgs()`

[IvoGoman]

These particular test cases do not call WithoutArgs() or WithArgs(). Only the internal queryBasedExpectation is manipulated to test the different behaviours.

[filikos]

Anyways, I will make a proposal to adjust many print statements since we can do some improvements on the UX of the library. Release will follow very soon

[filikos]

LGTM