Our tests are pretty chatty today. This makes it exceedingly difficult to determine what's going on and, when something failed, what that was. We need to do a full pass through them to enact changes to the following ends:

• don't repeat yourself - if code is making an asynchronous assertion or polling to make a change, never output the same message more than once
• honor $EVENTUALLY_VERBOSE - when running in CI, our tests should emit the minimal number of log lines
  • any log line that's announcing that the test will do something next should be quiet by default (${EVENTUALLY_VERBOSE} != "false") and only emit when running locally and the dev wants a streaming output
  • any log line that's announcing expected or wanted results, as opposed to failures or anomalies, should be quiet by default