[TASK] Move PHPStan from PHIVE to Composer

[oliverklee]

This allows us to have PHPStan extensions, e.g., for PHPUnit.

[JakeQZ]

Personally, on Windows, I've found PHIVE to be a PHAFF, though perhaps not fully understood the point of using it. It seems simpler to me if we just use Composer.

[oliverklee]

Personally, on Windows, I've found PHIVE to be a PHAFF, though perhaps not fully understood the point of using it. It seems simpler to me if we just use Composer.

The point was to avoid (or get out of) dependency hell, i.e., being able to run PHPUnit (which requires a composer install) on newer PHP versions even if e.g., PHP-CS-Fixer does not install on that version yet. (And, in the past, the tools did not support the PHP version range that PHP-CSS-Parser support, i.e., from 5.x to 8.3.)

We can also go full-Composer now and switch back to PHIVE when we gave problems like described with a newer PHP version we want to support.

[JakeQZ]

We can also go full-Composer now and switch back to PHIVE when we gave problems like described with a newer PHP version we want to support.

No, let's stick with PHIVE for the reasons you've given. Thanks for jogging my memory re the reasons for using it. All I could remember were problems with updates and caches. IIRC this was mostly solved by removing the binaries from version control, then it was just an issue of getting the local config right.