Re-add sigtest and downloadable zip to build; Run TCK in build

[BrentDouglas]

Firstly, this is based on https://github.com/WASdev/standards.jsr352.jbatch/pull/3 so please look at that before this one.

• Delete some eclipse config files. They didn't look important, everything can be run through maven now.
• Delete no longer used build.xml from tck module. It wasn't hooked up to maven so far as I could see anyhow.
• Add sigtest generation to tck modules pom. It was in the build.xml that was removed. These are not enabled by default as the JDK locations must be specified in a properties file and are enabled individually in build profiles. README.md has been updated with the details.
• Add batch.xml generation to tck modules pom. It was also in the build.xml that was removed.
• Update module com.ibm.jbatch.tck to build a jar that contains all the files nessessary to execute the TCK using the maven-dependency-plugin unpack goal, a common way of executing test's in third party jars. This will be a huge win for other implementations that might want to check their build against the tck. This is not currently possible as the tck jar in central doesn't contain the tests, the job.xml files or batch.xml.
• Add module com.ibm.jbatch.tck.dist to build the downloadable zip. This is needed to allow adding a dependency on the javadoc and sources jars of the tck module.
• Add module com.ibm.jbatch.tck.exec to execute the tck with the RI. This is not strictly necessary but IMO it makes it simpler to just run unpack in the test-classes directory knowing it will be empty and not going to overwrite any unit tests.

This might cause some merge conflicts with some of the other PR's, of so let me know when you merge them and I will rebase it.

[scottkurz]

@BrentDouglas - This is the next thing I'm looking at. Looks like you've done quite a bit here which I do greatly appreciate. Going to take me a couple sessions to digest it all, but just wanted to send a quick acknowledgement (2 months later!).

[scottkurz]

Brent, this is a huge help. Thank you! (When I get around to writing a TCK contributor guide I have to remember to give you a major credit for this work.)

I think you addressed all the key areas currently visible. There is also the build logic we used internally to convert the TCK tests to CTS tests, which I plan to share shortly but just haven't yet.

As the next step, I'm going to go ahead and merge this in, but not release to Maven just yet.

Then I'd like to give a bit more thought to how I will name the versions.... and do a bit more testing, after we which we can actually release this out there in Maven for others to consume.

Thanks again!

[scottkurz]

Appreciate if you can take a quick look at the result. I spent too much time messing around with the merge commits and messages and ended up pushing the result without checking again (for now). Thanks

[BrentDouglas]

A few minor things had changed since I wrote it. They are fixed in #28