Issue #1 Fix

This is my proposed fix for issue #1. I replaced start.sh with a start.py that allows specification of the wavsep install.jsp parameters, as well as alternate HTTP and AJP13 port numbers. I also altered the README significantly to explain invoking the script: https://github.com/dwvisser/pico-wavsep/blob/enhance/README.md
My concern here is that while the in-memory state of wavsep will be aware of the MySQL credentials, a later launched wavsep will have the database present, but no way to access it, since it hasn't been provided the credentials. 

I could be wrong. I don't know much about the wavsep internals. It's possible that if wavsep.war were placed in its own folder, and winstone was launched using `--webappsDir` instead, then perhaps that wavsep state would be sticky.