When it is determined that an error occured during the run of a launch
it's useful to have output from the process.
We just need to know what was going on in order to debug (if necessary)

Related to #2663 Complete browser log output when process isn't started

The tests ensuring a lower priority doesn't get logged were written in an
incorrect format so even changing the order in the LOG_PRIORITIES array
would not make them fail.

…changes

Commit 35965d9 changed the order of log priorities, making lots of
configurations no longer print console.log messages. This was a
backwards-incompatible change which this commit reverts.

Tests were added to ensure the proper order is respected.

Fixes #2582

fix(reporters): Revert the backwards-incompatible log priority order changes

feat(runner): Buffer stdout and stderr for output when errors occur

- Change use of for..in to plain for loop due to issues where array prototype is modified

Fixes #2671

fix(middleware): change to use vanilla for loop