Point XML issues from Lint to actual files.

This is likely a violation of how SonarQube is supposed to work; this is a java plugin
and probably shouldn't be generating issues for XML files. Works fine though with
Sonar Way XML plugin enabled on SonarQube though.

Maybe next step is to build two plugins from the sources: one for Java and one
for XML. That should satisfy SonarQube style of one profile for one language. It's a
bit suboptimal though, running Lint twice during the check, but it is what it is.
Use Lint 23.1.3