Feature/phpstan

[jeroenjans]

This PR adds support for PHPStan using the CheckStyleParser.

[codecov]

Codecov Report

Merging #21 into master will decrease coverage by 0.04%.
The diff coverage is 70%.

@@             Coverage Diff             @@
##             master     #21      +/-   ##
===========================================
- Coverage     80.84%   80.8%   -0.05%     
- Complexity     1371    1373       +2     
===========================================
  Files           225     226       +1     
  Lines          4684    4695      +11     
  Branches        375     375              
===========================================
+ Hits           3787    3794       +7     
- Misses          743     747       +4     
  Partials        154     154

Impacted Files	Coverage Δ	Complexity Δ
.../io/jenkins/plugins/analysis/warnings/PhpStan.java	70% <70%> (ø)	2 <2> (?)
...io/jenkins/plugins/analysis/warnings/YamlLint.java	37.5% <0%> (-5.36%)	0% <0%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update afb775e...1b1fcf2. Read the comment docs.

[uhafner]

Is the icon also available under an OSS or community license? It can be integrated as well if you like...

[uhafner]

private

[uhafner]

(I changed that in all other parsers as well:-)

[jeroenjans]

I've updated the visibility to private.
I've also rebased on master to resolve the merge conflict in the SUPPORTED-FORMATS.md file

[jeroenjans]

Regarding the image I haven't been able to find information on the license of the icon.
I'll see if I can get some information from the developers on this.

[jeroenjans]

Alright, I was able to check it with the developers and I was told that we can use the logo for this purpose.
I've added it in the last commit and updated the supported documents file.

[uhafner]

Nice, thanks! Can you please add a line or reference to the icon license (or to the discussion) in the LICENSE.txt file in the icons folder?

[uhafner]

And one more thing, can you add a small test case to ParsersITest that shows that your parser correctly finds n warnings. No need to check for individual properties, since this is done in the check style parser test.

[uhafner]

Thank you very much!