Add option to allow\disallow mocking methods unnecessarily for default expectations defined through quick definitions

[danydev]

…t expectations set through quick definitions

[robertbasic]

Hey @danydev, thanks for this PR! My biggest issue with it are the really long constant names that reduce the readability of the code, so I left some feedback to try and make it a bit better. What do you think?

[davedevelopment]

I keep getting lost between the issue (#1056) and this PR...

Regarding the API and it's extensibility, this is a very narrow use case, so I wouldn't worry about it. Mockery has been going a long time and you're the first to request this, so I'm not overly concerned about making the feature extensible going forward.

The names do look messy, maybe introduce a small object to wrap the quick definition settings?

Mockery::configuration()
    ->quickDefinitions()
    ->shouldBeCalledAtLeastOnce(); // pass a boolean to set, no args to get

[danydev]

@davedevelopment just performed the changes!

[davedevelopment]

I'm not a fan of methods that change semantic based on values of their parameters (i.e. "I'm a getter unless you pass me a value and then I'm setter"). But that's fine for me if that's fine for you.

Generally I agree, but I tend to let it slide for what I would consider to be PHP's lack of (reasonable) support for the Uniform access principle.

Will give @robertbasic a day to object, but I'm happy to merge.

[robertbasic]

This looks much better now, thanks @danydev!

[davedevelopment]

@danydev one last request, please could you add a quick note to the CHANGELOG.md file?

Thanks

[danydev]

@davedevelopment done