Broaden the scope of Thread.name inclusion to whole Request.call body

[jglick]

Looking at a thread dump, saw something like

"SupportPlugin periodic bundle generator: writing ….zip since …" …
   java.lang.Thread.State: WAITING (parking)
	at sun.misc.Unsafe.park(Native Method)
	- parking to wait for <…> (a java.util.concurrent.FutureTask)
	at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
	at java.util.concurrent.FutureTask.awaitDone(FutureTask.java:429)
	at java.util.concurrent.FutureTask.get(FutureTask.java:191)
	at hudson.remoting.Request.call(Request.java:188)
	- locked <…> (a hudson.remoting.UserRequest)
	at hudson.remoting.Channel.call(Channel.java:956)
	at hudson.FilePath.act(FilePath.java:1070)
	at hudson.FilePath.act(FilePath.java:1059)
	at hudson.FilePath.copyTo(FilePath.java:2234)
	at com.cloudbees.jenkins.support.api.FilePathContent.writeTo(FilePathContent.java:63)
	at com.cloudbees.jenkins.support.SupportPlugin.writeBundle(SupportPlugin.java:316)
	at com.cloudbees.jenkins.support.SupportPlugin.writeBundle(SupportPlugin.java:278)
	at com.cloudbees.jenkins.support.SupportPlugin$PeriodicWorkImpl.lambda$doRun$0(SupportPlugin.java:820)
	at com.cloudbees.jenkins.support.SupportPlugin$PeriodicWorkImpl$$Lambda$….run(Unknown Source)

It is unclear which agent is being waited for in this case. Request.call had helpfully been setting a Thread.name but this covered

remoting/src/main/java/hudson/remoting/Request.java

Line 177 in 95b2f7f

wait(30*1000);

but not for example

remoting/src/main/java/hudson/remoting/Request.java

Line 188 in 95b2f7f

lastIo.get();

in this case.

[jglick]

Preserving indentation of unmodified lines to minimize diff.

[jeffret-b]

Looks good. It help us locate additional information in some cases.

I'd be in favor of fixing the indentation to be correct.