fix: capture content written to stdout outside of report

[kzantow]

This PR adds handling to capture everything written to stdout. Syft has a guarantee (maybe an implicit one, for now) that all the content written to stdout is part of the report generated by the tool, such as ensuring JSON is valid JSON. Unfortunately, some libraries may write to stdout directly, such as this. In order to guarantee stdout only includes contents for the report, this PR captures this non-report output and trace logs it instead.

NOTE: although this PR uses the TRACE logging level, the behavior with a TUI when set to WARN would look like this:

$ syft -o json --platform windows/amd64 registry:mcr.microsoft.com/windows/servercore:ltsc2019 >stdout
 ✔ Parsed image                                                                                                 sha256:c632661e39bb365cf34bfdd943baa4ce5ba1ebdd713d790d1af0b9da20ae0bea
 ⠸ Cataloging packages             [0 packages]  
[0135]  WARN unhandled metadata table 38 File offset 0x944426 cols 5
[0136]  WARN unhandled metadata table 38 File offset 0xafdd82 cols 5
[0137]  WARN unhandled metadata table 38 File offset 0x1e720 cols 1
[0137]  WARN unhandled metadata table 38 File offset 0x45a cols 1