Bugfix: Continuous integration should be properly executed

[boesing]

Q	A
Bugfix	yes
QA	yes

Description

This will ensure that the CI pipeline for this project will run as expected. This also shows that Auryn container (as mentioned in #53) is not compatible with mezzio/mezzio (anymore).

This PR also contains the following changes:

• Removal of phpstan/phpstan
• Implementation for vimeo/psalm
• Removal of phpspec/prophecy
• Removal of composer.lock as part of the asset removal

[weierophinney]

@boesing I tried to resolve the errors that were occuring in your CI runs, got confused, and decided to start from scratch. I started by removing prophecy and switching to native PHP mock objects, following your examples as closely as possible.

What I ended up with was that the TemplateRenderersTest and the HomePageResponseTest had failures, and I was utterly unable to resolve them.

I started by getting errors about declare(strict_types=1) not being the first line of vendor/phpunit/phpunit/phpunit. Doing some sleuthing, it appears this happens when you call include() on a file that has a shabang line. When was that happening? I realized it was due to these tests having the @runInSeparateProcess annotation; for some reason, the autoloader was trying to load the vendor/phpunit/phpunit/phpunit during subsequent processes, which raised this error. (I think this is likely similar to the file_get_contents('./composer.json') file not found error you're seeing.)

So, I removed the annotation... and the first run for a given template renderer case would pass, but then it would start failing, generally for all other cases.

From what I could tell, it was an issue due to caching of the App\ConfigProvider class. Since this class is used to determine the paths to template files, the following would happen:

• Since the Laminas view renderer tests would run first, when it looked for Twig-related files, it was looking relative to the original installation directory in which we were testing Laminas view renderer. That directory would no longer exist (it was removed after those tests), so it could not find the files. When I commented out the logic that would cleanup after each run, it was finding the Laminas template files, but not finding the Twig files (as they were in a different installation directory).
• Since the Plates templates share the same suffix, I'd either get a file not found error (if I was cleaning up after each run) or I'd get errors with rendering due to unknown template methods and/or variables, because it was trying to use Laminas templates instead of Plates templates.

I can run each of those tests individually, and they pass. Running them as part of the test suite, they fail (due to cached class declarations). Running them in isolated processes fails (due to oddities with autoloading).

I'm not sure why this changes simply by switching from prophecy to native mocks. If I could resolve the @runInSeparateProcess issue, I think these would run fine, and I could finish up. For now, though, I'm stuck. ☹️

[weierophinney]

Closing in favor of #63 - I managed to get things sorted!