Possible bug in coverage variation tracking

[evilaliv3]

Hello we are noticing a possible bug in the codacy variation tracking.

As reference you could check:

• https://app.codacy.com/gh/globaleaks/globaleaks-whistleblowing-software/pull-requests/4573/coverage?utm_source=github.com&utm_medium=coverageSummary&utm_campaign=coverageSummaryPullRequest
• Fix issue #4570 globaleaks/globaleaks-whistleblowing-software#4573

As you may notice we provide the coverage with two calls collecting coverage reports, one for a component written in typescript and one for a component written in pythonthat compose a single application.
When you evaluate the coverage of the current commit you evaluate it correctly. (and the coverage results ~93%)
When you compare it with the coverage of the past commit instead you are probably comparing only one part of the coverage (and the coverage results around 70%; but the same commit was evaluated 93% when it was committed sending the coverage information with two components.)

Thank you if you could check into this and let us know your findings.