Getting rid of get_setting OS-specific scripts

Fixes for #1762, #1785, #1787, and a couple of unopened issues.

Our OS-specific scripts were doing hack-ish stuff to infiltrate our `settings.py` for the use within our OS-specific scripts.  Rather than put up this behavior, I slapped down those scripts, made them as dumb as possible, and pushed code into the python-side:
* Make all commands use the values from their `settings.py` files, rather than needing to have them passed in explicitly through our scripts.
* Have `kaserve` dump info about IP addresses/port at which the server is located
* Removing dependency of OS-specific scripts on `CENTRAL_SERVER`

Along the way, I fixed some bugs:
* Call `collectstatic` from `kaserve` on every cherrypy server start (since cherrypy doesn't use `STATICFILE_DIRS` like `runserver` does).
* Boost `CHERRPY_THREAD_COUNT` in `DEBUG` model, which was too low and causing slowness.

**Testing:**
 * Tested on OSX, not Windows (nor Linux directly).  Testing consisted of running `scripts/start.sh` and making sure both `chronograph` and `cherrypy` started, were running properly, and changed as I changed `PRODUCTION_PORT`, `CHERRYPY_THREAD_COUNT`, `CRONSERVER_FREQUENCY`.