Debugging browser tests: Hard to read console

... as an example; the `00:00 [32m+0[0m: ... [0m` is not super useful. I don't know if this means we should always use the `expanded` reporter for interactive debugging, or if there needs to be a different type of reporter for this.

Thoughts? @nex3 @grouma

Start by comparing the current browser-test console output with the expanded reporter mentioned in the issue and determine what interactive debugging output should show instead. Done means there is a decided reporter behavior that makes browser-test console logs readable, with coverage for the chosen output.

Written by the indexing model from the issue text.