Add phpbench to CI run to ensure that we don't accidentally break benchmarks

This is not indicative of performance, but just guarantees that the benchmarks
still run, and that we didn't break them during an upgrade or code change.

.travis.yml

@@ -62,6 +62,7 @@ script:
   - ./resources/scripts/cmd-proxy.sh composer phpcs
   - ./resources/scripts/cmd-proxy.sh composer phpstan
   - ./resources/scripts/cmd-proxy.sh composer psalm
+  - ./resources/scripts/cmd-proxy.sh composer phpbench
   - travis_wait 30 ./resources/scripts/cmd-proxy.sh ./vendor/bin/phpunit --verbose --coverage-clover build/logs/clover.xml
 
 after_success:

composer.json

@@ -73,6 +73,7 @@
     },
     "scripts": {
         "lint": "parallel-lint src tests",
+        "phpbench": "phpbench run",
         "phpcbf": "phpcbf -vpw --cache=build/cache/phpcs.cache",
         "phpcs": "phpcs --cache=build/cache/phpcs.cache",
         "phpstan": [
@@ -84,6 +85,7 @@
         "phpunit-coverage": "phpunit --verbose --colors=always --coverage-html build/coverage",
         "test": [
             "@lint",
+            "@phpbench",
             "@phpcs",
             "@phpstan",
             "@psalm",