JS-409 CssRulingTest change mvn verify -> mvn test

[zglicz]

JS-409

I noticed that at the end of the CssRulingTest we download some jars and try to publish a package. As @saberduck suggested, we could try to use mvn test instead of mvn verify.

[saberduck]

@zglicz did you check if this brings any timing benefits? I think it's quite risky change, I would keep it only if there are significant improvements and maybe let's start with Css ruling only at first

[sonarqube-next]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[zglicz]

Comparing: https://github.com/SonarSource/SonarJS/runs/32957225989 (last master) and this one
CSS ruling, now: 1:23, before: 1:36
plugin qa win1, now: 12:25, before: 11:40
plugin qa win2, now: 12:40, before: 13:25
win_sonarlint: now: 7:48, before: 8:25

So I wouldn't say conclusively that it is faster, but just the fact, that we aren't trying to package and run tests - which only includes maven IntegrationTest, which as I understand, we don't use...