Java module's external compiler types fail to catch IllegalArgumentException
thrown from the constructor of ExternalCompiler (a documented exception). They
let the exception propagate past CompilerType.prepareJob, which is not
permitted. More to the point, the up-to-date-badge code when creating a compiler
job permits this to be thrown, and so IAE's can appear even when the user is not
doing anything.

This blocks a fix of #11367. Rather, that bug can be fixed, but when this is
done, any Java source which does not correspond to a file on disk (e.g.
un-checked-out VCS file, or any normal template) will cause an exception dialog
to appear when it is recognized and the badge is calculated. The dialog is
annotated with a localized message, so it is polite, but still makes no sense
that it should appear.

Suggest Java module implement fix similar to the one in Ant module very recently
(AntCompilerType):

1. All compiler types should check for possibility of IAE from ExternalCompiler
constructor, explicitly catch it, and if caught, do nothing immediately, but if
the compiler job is run, then print out a message to the user based on the
localized annotations. This requires a special compiler & group. See
AntCompilerType.BogusCompiler for an example.

2. Code to check compiler badges should probably catch RuntimeException just to
be safe, and log it at low level (log file, e.g.), since it is clearly harmless
if the compiler job could not be created correctly in this case.