FIx release issues

Feeback from Ate:

• The wookie-parser wookie-java-connector jars (all 3 types) come with a LICENSE file listing way too many 3rd party licenses. Most likely these LICENSE files only need to contain the Apache license itself as/if no other 3rd party licensed source or binary is contained in them.

• The provided pom files all have a <scm> definition pointing to the wookie svn trunk location, these should preferably point to the actual (and final) tag location where this release sources can be found.
  Note: the way the Wookie release currently is done/prepared using a (temporary) branch makes this a bit difficult as during the release period the final tag location (e.g. /wookie/tags/0.9.1-incubating) doesn't exist yet!

The typical/common release procedure is to first create the final tag, and then/thereafter produce the (final) release candidate artifacts from that tag.
It is also not recommended to modify a tag once created, so 'fixing' a release candidate which already is up for vote (or worse: afterwards) is seen as bad practice/pattern as it makes the tag 'unreliable' and more difficult to verify if it still is the same as downloadable source distribution to be verified.

• The src, -standalone and -war distributions have an embedded root folder called "Apache-Wookie". A more commonly used pattern/format is "apache[project]-[version]" (all in lowercase) similar to or same as the distribution name itself.

That is less dangerous and easier for the end user so that extracting distributions keeps different versions nicely separated without potentially overriding each other.