Change the client transport method name from "websocket" to "flashproxy".

Both names still work and are equivalent. This only affects what string
appears in the configuration files we ship.
move appengine and facilitator docs to facilitator subtree
Move the modules directory into the proxy directory.

Taken from
https://github.com/infinity0/flashproxy/commit/4819df2aa1f45eec0fd5e676abcb013ac5e2963f,
except moved to proxy/modules rather than proxy-modules, as was
originally suggested at
https://trac.torproject.org/projects/tor/ticket/9668.
Move gmail-setup.txt to gmail-howto.txt to match other docs.

appengine-howto.txt already referred to gmail-howto.txt.
ChangeLog for source code rearrangement.
Ticket number for source code rearrangement.
separate child tests and link in future websocket-transport tests
use GNU autotools to create an installable package, including docs
add reference install scripts and integrate them into the instructions
install the appengine files as data files in $(pkgdatadir)
populate /etc/flashproxy during post-install, including generating keys
handle initscripts in a more robust way and provide an option not to install them
return INSTALL to a site-local install, add openssl as a dependency
embed gmail password placeholder directly in Makefile to be less confusing
disable initscripts by default since it ignores ${prefix} and causes `make distcheck` to fail
better instructions making use of the existing option
readd check target and change the test port so as to not conflict with existing service
source the email address from a defaults file, don't hard code it
don't change owner of secret files; they are read by root and then privileges are dropped
use automake's python test runner