Implement stdout report formatting

[matejchalk]

Follow-up to:

• Design: Improve stdout for CLI #151

PoC:

• PoC - stdout design #189
• implementation in tools/pocs/stdout-report-mock.mjs

Structure

For visual details (alignment, spacing, colors, etc.), refer to PoC implementation linked above.

• for each plugin:
  • plugin title as heading (with audits suffix)
  • list plugin's audits:
    • ● colored red/yellow/green based on audit's score (thresholds are 50 and 90, same as for Implement report.md formatting #148)
    • audit title
    • audit display value (or raw value if missing) - highlighted (bright cyan)
• Categories heading
• table with each category:
  • category title
  • formatted score (0-100) in bold with red/yellow/green coloring
  • total number of audits (from category refs with "expanded" groups - same as Implement report.md formatting #148)

Implementation notes

• chalk for colors and bold formatting
• cliui for columns (audits)
• cli-table3 for table (categories)

Design

[BioPhoton]

● colored red/yellow/green based on audit's score (thresholds are 50 and 90, same as for #148)

I miss informative audits in ⚪️ color

[matejchalk]

● colored red/yellow/green based on audit's score (thresholds are 50 and 90, same as for #148)

I miss informative audits in ⚪️ color

It can't apply here, because all audits are listed irrespective of which categories reference them. Audit weight 0 only applies when referenced in a category. It could apply to a category detail section, but I didn't include that in the stdout, I wanted to keep it more streamlined (stdout is most concise representation of the data, markdown is richer and portal is most rich), but also have useful information when a user hasn't configured categories yet (seeing the stdout is part of the 1st contact).

[BioPhoton]

seeing the stdout is part of the 1st contact
Yes