build(ci): improve unit test summary

[david-allison]

Purpose / Description

I didn't like the look of the markdown tables now we've added more modules

Approach

• Fix markdown issues with multiple suites
• Combine the individual tables
  • Via appending, rather than accumulating the results

How Has This Been Tested?

Before:

After:

Learning (optional, can help others)

The complexity to run a script using the newer replacements for gradle.buildFinished { } wasn't worthwhile

Checklist

• You have a descriptive commit message with a short title (first line, max 50 chars).
• You have commented your code, particularly in hard-to-understand areas
• You have performed a self-review of your own code
• UI changes: include screenshots of all affected screens (in particular showing any new or changed strings)
• UI Changes: You have tested your change using the Google Accessibility Scanner

[mikehardy]

looks nice

The complexity to run a script using the newer replacements for gradle.buildFinished { } wasn't worthwhile

Amen to that, it is so annoying that there is no simple hook for "do this at the end", it's a ridiculously complex set of providers and OO/IoC ivory tower junk. Not a fan.