Allow additional bundle options to be set during build

[paulhoadley]

It's currently quite tricky to get certain JVM options set at application launch time. The launch script does some gymnastics to get JVM options into the right place on the command line: those starting with -X, for example, end up in the right place (that is, prior to the class name). But some, like the old -server and newer --add-exports are not moved into the right place by the launch script. The launch script will honour the JVMOptions line in the header of the *ClassPath.txt files, but there's currently no mechanism for setting this using wolifecycle-maven-plugin.

So, all this pull request does is to update wolifecycle.build.xml to set the following when the woapplication Ant task builds the bundle:

• jvm
• jvmOptions
• jdb
• jdbOptions

Their values are pulled from properties of the same names, so you can set them in build.properties:

jvm=foo
jvmOptions=bar
jdb=bar
jdbOptions=quux