Shrink space used by JaCoCo

[Cervator]

Takes a good 40 MB per build of the plain Terasology job, which is likely unaffected by build archiving. Something that can be cleaned up post-build without affecting the listing of JaCoCo results?

One potential alternative is using a different hosting service for code coverage results then not storing the stats in Jenkins