Avoid building debug or trace log messages unless the respective log level is enabled

While debugging the performance of a large GraphX connected components computation, I found several places in the network-common and network-shuffle code bases where trace or debug log messages are constructed even if the respective log level is disabled. Refactoring the respective code to avoid these constructions except where necessary led to a modest but measurable reduction in task time, GC time and the ratio thereof.