[HUDSON-5073] point the user to the slave log if the build failed because the slave went offline during the build.

when setting outerHTML, the element itself is replaced, so we've been applying behaviours to the wrong tree.

[HUDSON-5073] if the build fails because the node went offline, point the user to the slave log where the details are.

This change might reveal additional information about why the connection is disrupted.

Regrettably the CLI client and the CLI server are in the same package, and this doesn't work very well with i18n scheme as we end up having two classes of the same name (and one hides the other in the server.)

So I'm renaming the Messages class on the client, but not the classes itself for compatibility

See
http://groups.google.com/group/hudson-users/browse_frm/thread/4272c82edb5460b8
"Install-plugin CLI action doesn't work when an URL is specified as
SOURCE"

An investigation on NECTAR-50 revealed that the dead lock prevention made in 02fbfd9e and c5269550 are causing slow down by having too many threads go through scouting, which in turn calls into classloader (which is synchronized.) Reduce the overhead by reusing sezpoz index so that classloading overhead is minimal.

[HUDSON-8493] MavenReporter#postExecute parameter Throwable error is always empty in case of mojo failure