[TASK] Coverage report with attributions

[caleb-sitton-inl]

---

Issue Description

Is your feature request related to a problem? Please describe.
While coverage tracking is helpful for understanding the code tested, as it is currently set up in HERON, it does not allow developers to see which tests are contributing to each line's coverage. A particular application where this change would be helpful is for the new DOVE repository, which takes over the dispatch currently performed in HERON. By understanding the way dispatch is tested in HERON, a new test suite in DOVE can be more efficiently crafted.

Describe the solution you'd like
A new coverage script that specifically tracks which tests run each line would be ideal.

Describe alternatives you've considered
I don't see an easy way, with the latest version of coverage.py, to have the standard coverage script track contexts.

---

For Change Control Board: Issue Review

This review should occur before any development is performed as a response to this issue.

• 1. Is it tagged with a type: defect or task?
• 2. Is it tagged with a priority: critical, normal or minor?
• 3. If it will impact requirements or requirements tests, is it tagged with requirements?
• 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
• 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

---

For Change Control Board: Issue Closure

This review should occur when the issue is imminently going to be closed.

• 1. If the issue is a defect, is the defect fixed?
• 2. If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
• 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
• 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
• 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?