Quieter Integration Tests

[zeripath]

The integration tests produce far too much logging when they're running, so much that you cannot easily find errors.

This patch redirects the logging and adds some information to each test to print which test is running.

It requires that each integration runs PrintCurrentTest. (This has been added to prepareTestEnv.)

[codecov-io]

Codecov Report

Merging #6513 into master will increase coverage by 0.12%.
The diff coverage is 93.01%.

@@            Coverage Diff            @@
##           master   #6513      +/-   ##
=========================================
+ Coverage   40.27%   40.4%   +0.12%     
=========================================
  Files         403     404       +1     
  Lines       54079   54089      +10     
=========================================
+ Hits        21781   21852      +71     
+ Misses      29279   29224      -55     
+ Partials     3019    3013       -6

Impacted Files	Coverage Δ
modules/log/flags.go	100% <100%> (ø)
modules/setting/setting.go	48.16% <100%> (-0.38%)	⬇️
modules/log/smtp.go	89.36% <100%> (ø)	⬆️
modules/setting/log.go	73.48% <100%> (+9.85%)	⬆️
modules/log/file.go	75.52% <100%> (ø)	⬆️
modules/log/conn.go	96.55% <100%> (ø)	⬆️
modules/log/colors.go	66.9% <37.5%> (+5.83%)	⬆️
modules/log/console.go	75% <66.66%> (ø)	⬆️
modules/log/writer.go	97.39% <97.39%> (ø)
models/unit.go	0% <0%> (-14.29%)	⬇️
... and 10 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7ed65a9...b843d8b. Read the comment docs.

[zeripath]

On test failure the logs will be outputted Unfortunately they will be prefixed with a reference to the new wrapped logger, but I'm not sure there's a way to avoid this without rewriting the go testframework.