Coverage reports use internal Cadence location IDs instead of source file paths, breaking LCOV tooling

Coverage reports use internal Cadence location IDs instead of source file paths, breaking LCOV tooling: a task in MiMo-V2.6-RL-harbor-code: MiMo-V2.6-RL Code (Harbor) (Harbor dataset). I'm working on a Flow dApp written in Cadence and using the testing framework to run unit tests against my…

The task

I'm working on a Flow dApp written in Cadence and using the testing framework to run unit tests against my contracts. I configured a `CoverageReport` and exported it both as JSON and as LCOV so I could hook it into the standard coverage tooling we already use elsewhere (genhtml, Codecov, Coveralls, etc.).

Part of FineEnvs/MiMo-V2.6-RL-harbor-code.