What you want to do is read each module's test report. You can do that with multi-module project configuration. It will probably be most straight-forward if you handle it all from your main build.xml. I've not tested this from Ant, but something like this should work
<property name="sonar.projectKey" ...
<!-- all normal properties here -->
<property name="sonar.modules" value="module1,module2..." />
<property name="module1.sonar.jacoco.reportPath" value="...
Note that if the Jacoco reports are all in a standard location, you may not even need to specify them because child modules inherit their parents' properties. The docs for multi-module project configuration aren't written with Ant syntax in mind, but you should be able to work through that as long as you keep this in mind from the SonarQube Scanner for Ant docs:
The SonarQube Scanner for Ant is an Ant Task that is wrapper of SonarQube Scanner, which works by invoking SonarQube Scanner and passing to it all properties named following a sonar.*
convention. This has the downside of not being very Ant-y, but the upside of providing instant availability of any new analysis parameter introduced by a new version of a plugin or of SonarQube itself.