Remove problematic test case

[jseparovic1]

Reverts only part of #316

Following test case produces different phpstan analyisis output depending on used versions:

  public function testCreateProphecyInline(): void
    {
        $prophecy = (new Prophet())->prophesize(Src\BaseModel::class);

        $prophecy
            ->getFoo()
            ->willReturn('bar');

        $prophecy
            ->doubleTheNumber(Argument::is(2))
            ->willReturn(5);

        $testDouble = $prophecy->reveal();

        self::assertEquals('bar', $testDouble->getFoo());
        self::assertEquals(5, $testDouble->doubleTheNumber(2));
    }

Creating Prophet inline seems like a valid use case that should be supported as well. In combination with PHPUnit 10.0.0. this produced internal phpstan error due to following lines. I added the test case thus this use case is visible and supported however output is different based on combination of versions thus it is hard to support this without having version specific baseline(s).

More developers are reaching for this use case as PHPUnit 10 deprecated non-static data providers (see sebastianbergmann/phpunit@9caafe2). Easy way out is to use (new Prophet()) .

[jseparovic1]

@alexander-schranz As per discussion in #285 I opted to use approach that includes minimal changes to make the build green. Let me know what do you think :)

[ivan-wolf]

This replaces #327, correct?

[alexander-schranz]

Fine for me currently, is there still a way we could test this?

[jseparovic1]

@alexander-schranz Test case described in the issue is one that is verifying this functionality and it should be included (sooner or later). Currently only limitation is different phpstan output which we could add and create CI matrix to test it as well. Moreover if support is dropped for older PHP versions output might be more consistent.