topcat: fix broken screenshot

Poorly edited multi SIA window screenshot had some pixels out of place.
Paste over them.
topcat: stop doing auto-conversion of time columns

The Conversions class can automatically convert string columns to
numeric ones.  But the newer DomainMapper machinery does the same thing.
These do not play nicely with each other, and in particular make
Time plots in topcat (but not stilts) fail for ISO-8601-formatted time
coordinates.  Hack round this by turning off time conversions in
the Conversions class.  This will break some things, for instance
statistics calculations and plotting in non-time plots for
ISO-8601 columns.
However, these didn't work particularly well before (the values
were just interpreted as decimal years AD), and I'm hoping they
weren't much used.

In the long term, I think the Conversions class should be phased out,
replaced by more pervasive use of DomainMappers.
But another possibility would be to specify what kind of conversion
is required when it's used (in ColumnDataComboBox).
vo: trim line responses from UWS services

For single-line responses like the output from the {jobs}/(job-id)/phase
UWS endpoint, add a switch to trim trailing whitespace from the result.
The GACS TAP service was returning phases like "COMPLETED\r\n" which
didn't match "COMPLETED" that I was looking for.  I don't know whether
this trailing whitespace is strictly legal, but I posted a message
on the GWS mailing list to find out, with no response, so give GACS
the benefit of the doubt for now.
cdf: build CDF javadocs as part of javadocs-full target
ttools: add some programmatic invocation example classes
ttools: fix bug in explicit ranging for sphere plot
ttools: move some line-wrapping code

Move some line wrapping code from OutputModeParameter to Formatter so it
can be re-used elsewhere.
ttools: improve custom description for table input params

Some table input parameters (AbstractTableInputParameter and subclases)
need custom wording in their parameter descriptions and prompts to
explain the purpose of the tables in question.  This was previously
handled by some extremely nasty string manipulation that relied on
knowledge of hard-coded description text.  Replace it by some more
reasonable configuration methods.
ttools: refactor Plot2Task

Split Plot2Task up into an abstract superclass (AbstractPlot2Task)
and a PlotType-agnostic concrete subclass (GenericPlot2Task).
GenericPlot2Task should now behave just the same as Plot2Task used to.

But now I can instantiate AbstractPlot2Task separately for particular
PlotTypes, to give PlotType-specific plotting classes that provide
better self-documentation and are easier to use (parameter lists
customised to particular plot types).
ttools: add PlotterParameter

The layerN parameter is now provided by a custom parameter
type PlotterParameter.  The values of this parameter no longer
map 1:1 to Plotter instances, since it previously had far too many
possible values
(mark-auto, mark-flat, mark-aux, ... link-auto, link-flat, link-aux, ....),
which made it unwieldy to (auto-)document.

Now, for the special case of ShapeModePlotters, this parameter
just specifies the ShapeForm, and an auxiliary (shading) parameter
is used to specify ShapeMode.  For other plotter types, this parameter
specifies the Plotter in full.
ttools: make layer suffixes optional in plot2 task parameters

Allow data and style parameters to be specified either with or without
the layer suffix.  This generally means much less typing for multi-layer
plots where the layers are related (e.g. from the same table).
ttools: fix plot2task to handle per-layer DataGeoms
ttools: add typed plot2 task

TypedPlot2Task allows much better self-documentation.
Added a couple of example subclasses (Plane and Sky).
Other type-specific ones left to do, but most will be trivial.
ttools: add PlotUtil.subtractInsets utility method
ttools: allow data insets to be set on a PlotDisplay

You can now fix the extent of the region between the data part of the
plot and the component boundary for a PlotDisplay.
Previously it only worked for exported icons.
ttools: add data insets capability to example plot classes
ttools: replace plot2task boost parameter with compositor

Replace the (floating point) alpha boost parameter in AbstractPlot2Task
with a more general parameter with type Compositor.  This usually
works the same way, but allows you to use custom Compositor objects
pluggably at runtime if required.

Needed to make the BoostCompositor class public rather than just
having a static factory method Compositor.createBoostCompositor.
This allows other components (the stilts parameter system) to
identify BoostCompositors as such and determine their boost values.
ttools: first tranche of Plot2Task parameter documentation

Add required documentation (prompt and description) for the parameters
explicitly defined in the AbstractPlot2Task class.
This does not cover those parameters constructed automitically
from Coords or ConfigKeys.
ttools: add entity declaration options to Formatter

Provide the option to declare some internal entities to the Formatter
class for it to use while parsing XML it's going to format.
I ended up not using this, but it might possibly come in useful at
a later date, so leave it in.
ttools: parameter documentation now includes value class

The auto-generated parameter documentation (in SUN/256 and on the
console using the help parameter) now include information about
what class the parameter represents.  This is useful/necessary
for programmatic use of the parameter system, since you may want
to submit typed values to a MapEnvironment as an alternative to
string values, so you need to know what type is permitted.

However, this is a bit problematic, since for the first time the
TTOOLS API is being exposed in the STILTS UI.  Various issues
with that, including the fact that the javadocs are not currently
shipped as part of the STILTS package, which they really should be
if some of the classes are relevant.  In the long term, I'd like
to split the plot2 classes out of STILTS altogether and expose
only that API, but in the meantime, reference the javadocs
published from my web page as a stopgap.

I'm also not quite sure about the aesthetic presentation of the
parameter types in the Usage sections of the auto-generated task
documentation.  Maybe revisit the details at some point.