[JENKINS-19004] set name of remoting threads
Log CannotResolveClassException and similar at FINE, not WARING.
OldDataMonitor already collates these errors and presents them to the user with a fix.
Printing a stack trace for each and every missing class just clutters the log file.
(Especially when restarting after disabling a widely-used plugin.)
Merge pull request #895 from kutzi/JENKINS-19004-channel-executor-name

[JENKINS-19004] set name of remoting threads
[maven-release-plugin] prepare release jenkins-1.528
[maven-release-plugin] prepare for next development iteration
updated changelog for release
updated changelog as a part of the release
merged back the RC branch
avoid log duplication with mvn 3.1 builds
add changelog entry