Workaround for issue 21654 - CodeCov build already finished

[MoonlightSentinel]

Try adding the Azure/Cirrus jobs to the job count and expected CI's.

Upstream issue: codecov/codecov-bash#411

[dlang-bot]

Thanks for your pull request and interest in making D better, @MoonlightSentinel! We are looking forward to reviewing it, and you should be hearing from a maintainer soon.
Please verify that your PR follows this checklist:

• My PR is fully covered with tests (you can see the coverage diff by visiting the details link of the codecov check)
• My PR is as minimal as possible (smaller, focused PRs are easier to review than big ones)
• I have provided a detailed rationale explaining my changes
• New or modified functions have Ddoc comments (with Params: and Returns:)

Please see CONTRIBUTING.md for more information.

---

If you have addressed all reviews or aren't sure how to proceed, don't hesitate to ping us with a simple comment.

Bugzilla references

Auto-close	Bugzilla	Severity	Description
✗	21654	normal	CodeCov build already finished

Testing this PR locally

If you don't have a local development environment setup, you can use Digger to test this PR:

dub run digger -- build "master + dmd#12221"

[RazvanN7]

So upstream fails because we are sending more than 1 request? Then why are Azure and Cirrus added to the list of jobs?

[MoonlightSentinel]

So upstream fails because we are sending more than 1 request?

CodeCov apparently thinks that all builds were submitted and fails when it receives a delayed report. Not sure why it suddenly started failing...

Then why are Azure and Cirrus added to the list of jobs?

To sync the list of CI providers with the actual pipelines

[RazvanN7]

So the issue was that codecov was expecting only one report from circleCI whereas we were sending 3. The first one was taken into account and when the second one came the issued an error?

[MoonlightSentinel]

The CI currently creates five coverage reports (1 CircleCI + 1 Azure + 3 Cirrus).
But the upload usually failed for CircleCI, even though it was already listed as an expected CI.