Investigate replacing Batik CSS

[spassarop]

Investigate replacing the CSS parser with something newer, more transparent and more open. Currently there are issues that result in wontfix caused by Batik doing things internally we can't see/change/affect.

This is useful to link/reference all issues related to Batik being a dependency.

[carlosame]

Switching to an alternative SAC parser should be trivial, and a few years ago I made a couple of SAC benchmarks which may be of interest here:

https://css4j.github.io/sac-mark.html

There is also the possibility of migrating to the newer NSAC api, which has explicit support for the latest CSS specs, but that would be a bit more work:

https://css4j.github.io/api/latest/io.sf.carte.css4j/io/sf/carte/doc/style/css/parser/package-summary.html

and please note that css4j is not published to Maven Central so you'd have to add a repository section to your POM file, pointing to the Maven repo at https://css4j.github.io/maven/.