Add actual function that can be mocked in PHPUnit 12

[crocodele]

See php-mock/php-mock-phpunit#75.

[michalbundyra]

@crocodele thanks for this PR. Before I publish stable version I would like to make sure that it all works with current versions of our satellite packages - phpunit, prophecy and mockery.
All these changes here are internal and I believe there is no BC Break, but just to make sure we are still fine with other packages.
I'll create beta release so then we can try the other packages with beta, and once we get there working PRs I'll publish a stable.

Would it work for you?

Thanks

[michalbundyra]

@crocodele please see: php-mock/php-mock-phpunit#77

It looks like it's not working atm. I haven't tried mockery or prophecy yet, feel free to try if you have a minute. Thanks

[crocodele]

Cheers @michalbundyra!

I suppose this will require a breaking change and hence a new major version 3.0.0, because in php-mock-phpunit:

1. addMethods() can no longer be used now that the method is actually in the class (Trying to configure method "sqrt" with addMethods(), but it exists in class "phpmock\integration62570404d3773f165e00844cef2e111a\MockDelegateFunction". Use onlyMethods() for methods that exist in the class)
2. getMockForAbstractClass() probably fails too now that the class is no longer abstract.

I updated the PR in php-mock-phpunit to use 2.5.0-beta1, let's see if the tests now pass. 🤞

I'll also have a look at php-mock-prophecy and php-mock-mockery to see if any changes are required there.

[michalbundyra]

@crocodele actually I am thinking if we should even create a method in the class, when the function name is null?

I am not really sure why we even allow the function name to be null here, and it looks like the null value is not even used in the satellite packages.

Also I wonder if we should be creating the method with a signatureParameters? As I see all seems to be working fine without the 'correct signature' tho 🤔