Feature Request: support mypy coverage reports

In the current version (0.40.0), if I use any report generation options in mypy.ini , it doesn't display the report for the entire run.
It seems to only display the report last targets that it processed.

Expect: Output of aggregated of all targets that it checked
Actual: Output of some targets (presumably the first or last targets it checked)

Ideally, this can be integrated with https://bazel.build/configure/coverage or other existing tooling for tracking and tooling that improves visibility of coverage data (such as Sonarqube).

No file or test is named. Start by locating report generation in rules_mypy and reproduce the mypy.ini report behavior across multiple Bazel targets. Compare the output with the expected aggregation across all checked targets, then verify whether the result can connect to Bazel coverage or existing reporting tools such as SonarQube.

Written by the indexing model from the issue text.