Report on test coverage

[72636c]

This is just the first step of dumping a coverage table out to a Buildkite annotation and GitHub check run. We can later build towards:

• Providing Buildkite annotations of failing tests
• Providing test coverage as a GitHub PR comment
• Comparing test coverage against the default branch per Annotate test coverage #652

[changeset-bot]

⚠️ No Changeset found

Latest commit: 39441a9

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[72636c]

@samchungy how do you feel about having this reporter support both Buildkite and GitHub 😬

If we want coverage integrations across both, it may be wasteful to define two reporters and to run renderCoverageText twice.

[samchungy]

I don't love it but renderCoverageText is kinda costly I guess. Even the loop processing this I guess.

Do reporters run in series? I wonder if we could store it in memory? 🤔

If we do this -> might want to rename the reporter? maybe reporters/annotate/index.ts?