Nearly working artifactory publish

The artifactory-publish resolver can now be used
from the `release-hudson` target to publish all
the OMERO jars to the OME artifactory repo. The
only parameter needed is a password for hudson.
Override 'artifactory' target in insight

Since insight does not produce all the artifacts
upfront, the target needs to be overwritten like
the `install` target and "haltonmissing" passed.
Omit Bio-Formats component

Since Bio-Formats jars/poms are pushed via
a separate job, the release-hudson target
will now skip that component.
Make repository name configurable

Now, by using `ant release-hudson -Dartifactory.repository=foo`
or setting the same in etc/local.properties a repository other
than ome.staging can be used. Most useful is setting it to
ome.unstable for merge builds or ome.snapshots for latest builds.
Make artifactory username configurable
changingPattern is now SNAPSHOT not DEV
Load local properties last (overwrite)
Add classifier to publish resolver
Don't publish ivy files (workaround)

For some reason, the ivy.xml files are being uploaded
with "SNAPSHOT" in their names rather than with the
artifactory-specific timestamp. This requires the user
having the "delete" permission, so instead, we're
holding back that artifact.
Deploy only maven-like artifacts

This skips zips and other "release" conf style
items which tend to be large. Instead, only the
main jar, the pom, the sources, and the javadocs
should be uploaded for each component.
Merge pull request #2609 from joshmoore/rebased/develop/artifactory-deploy

Artifactory deploy (rebased onto develop)