Refactor unit tests scraping stdout/stderr in cases where alternatives are available. #7458

As noted here:
#7234 (comment)

Scraping stdout and stderr, often from running a code sample in a subprocess, is error prone and ideally this should be avoided where an alternative exists (e.g. closing over the expected string and asserting its presence in some other way as part of the code sample being executed).