Move reports across commits

[aj-codecov]

https://codecov.canny.io/admin/feedback/customer-requests/p/ability-to-move-reports-across-commits

A XXXXXXXX request

They want to be able to take the coverage of one commit and move it to another - implementation could be CLI based at first, that's likely the easiest path forward

[rohan-at-sentry]

I'd support tackling this in Q4 2024 (we're already underway with Q3). This will help in the following scenario

Our scenario is that we can't upload to Codecov on post-merge since we don't want to run another post-merge CI/CD pipeline. The commit landing on the main branch already went through our mergequeue system and has a perfectly valid coverage report.
As of today, the flow looks like this, with a lot of extra steps in both our CI & postmerge:
CI runs tests, generates coverage report, uploads to Codecov,
CI stores report internally,
PR lands, kicks off a job
Job fetches report from storage, reclones Git repo, reuploads to Codecov with new commit SHA
The ideal flow would be:
CI runs tests, generates coverage report, uploads to Codecov,

if I analyze closely, this pain should be something all larger customers currently feel (explained by most commits not having a "base report" to pick from , and not just isolated to 1 customer. A merge commit not running CI (because everything until then is tested) is totally reasonable, and we should consider expanding our processing capabilities to account for this workflow.

[rohan-at-sentry]

Quick workaround (?) (courtesy @drazisil-codecov ) - modify existing worker logic to not only look for a single parent, esp if that parent doesn't have a coverage report