Render results to job summaries

Grouped by the upstream. For example, a Gradle group, Kotlin group, JB Compose group, and even an internal dependency group. Probably inside a ``, so that you can pick which axis you care about and then grab the summary to copy elsewhere. Include links to failing builds and the project repos.

This will be used for filing issues and reporting status to places (such as Kotlin EAP).

No file or test is named in the issue. Start by tracing where test results are currently rendered or exported, then define the grouping axes and summary format using the Gradle, Kotlin, Compose, and internal-dependency examples. Done means summaries can be copied from expandable sections and include links to failing builds and project repositories.

Written by the indexing model from the issue text.