In WT-16037 we add Python disagg base tests to code coverage tracking. While it's a good starting point to have some disagg tests tracked by the existing code coverage tasks, and generate a "meshed" coverage report, having a disagg-only coverage report generated is expected to help us analysing the coverage reality of disagg-only code logics (possibly breakdown to modules), which can serve as a reference for teams to evaluate and determine future testing improvement effort.

Outcome:

• Have a set of disagg-only code coverage tasks running disagg-only tests, and generate a disagg-only coverage report.

Note: the analysis using the generated disagg-only coverage report is expected to be an  one-off manual effort, and is not scoped in this ticket.