check for existence of isatty to account for older wsgi Log objects
Add BCFG2_CONFIG_FILE environment variable (regression from 1.3)
Remove unused import
Parse the config inside of the wsgi application function

If you don't set this, the parsing code will always look in
/etc/bcfg2.conf for the config, which might not exist or be readable by
apache in a standard config.
Reporting: update non-ORM bits to know about separate database

There is a little bit of code in the reporting web interface that
uses raw SQL rather than the django ORM.  This bypassed the database
router functionality (since there is no model to bind to).  Django
supports keeping track of multiple connections in the raw SQL interface,
so this commit does the refactoring necessary to support the multiple
databases.
Handle the case where BCFG2_CONFIG_FILE isn't set in the environment
don't trigger full reparse on adding config file

The full reparse turns out to be unnecessary with one change to
the server options, and plays havoc with ordering of django components
and overriding values in bcfg2-web.conf