Add Permissions to manifest (required for webstart)

Also added Codebase (currently * allows running from anaywhere) and Application-Name (displayed in the webstart dialog, instead of the user-unfriendly classname)

Conflicts:
	components/insight/build/dist.xml
Add Trusted-Only:true to the Insight manifest.

See http://docs.oracle.com/javase/6/docs/technotes/guides/jweb/mixed_code.html#trusted_only
Don't sign the webstart jars by default.

We're going to be code-signing in a separate process, so this prevents jars being double-signed, once with the self-signed cert and once with a proper one.

The webstart-sign target is still there, so you can use `./build.py webstart-sign release-webstart`.
Add an external webstart signing script

Automatically run this script with the existing self-signed certificate as part of the standard docs/hudson/OMERO.sh build
cd target/ before doing the code-signing

This is so that ./build.py clean will remove any logs or temporary directories
Disable jar-signing in update-version target

Conflicts:
	build.xml
Use system proxy environment variables
Add verbose option (prints out full jarsigner command)
Check jarsigner is executable
Log proxy args and directory to be zipped. Warn about password logging.
Allow jarsigner without args to return 0 or 1

Return code depends on Java version
Change check_jarsigner error message (since exit 0|1 is allowed)

Just in case any pedants are reading
Merge pull request #2238 from manics/webstart_codesigning-dev_4_4

Webstart code-signing 4.4. Merging for release of 4.4.11.