initial revision of python client

Jenkins: http://jenkins.buttonweavers.com:8080/job/buttonmen-cgolubi1/296/

This is not a full client implementation of the API, but it's a start.  It contains three sample python scripts:
* create_game: gets skill information and creates random games of various types
* game_info: prints compact "who's playing who" information about a game
* monitor: loops looking for games that are waiting for your attention, like the monitor functionality on the old site

These scripts rely on two python modules:
* bmapi.py: this is a fairly strict python implementation of a subset of API functions.  It uses cookie files to cache credentials so that it can operate, and uses an ini-format config file which can contain credentials and cookie files for one or more sites (e.g. i have www, dev, and my local vagrant instance, in mine)
* bmutils.py: wrappers that i find useful for the bmapi.py routines.  These may or may not be to other people's tastes, and don't strictly conform to the API.  They are strictly wrappers, i.e. the stuff in bmapi.py is what makes all the actual API calls.

Since bmapi.py is the API implementation, that's what we need to unit test, so i added a test script using python's unittest module, and hooked it into both run_buttonmen_tests (for vagrant/cli testing) and the jenkins build.xml (for regression-testing of future pulls).  This should mean that if we modify the API, the unit tests will remind us to update the python client too.