since this is PsiturkOrgServices, I don't think it needs a configurable ad-server location

- hard coding all the server and api domains to ___.psiturk.org
needs requests library now
a rough idea of how psiturkservices works now

- this hasn't been tested yet since waiting to see what changes we make to config file structure
deleting ads not necessary
moving a few things around, and making new psiTurk access section
new config options necessary for ad server
brewer controls no longer only about IE, so updating error messages
changes to use the "live" ad server

- update to a couple of the field names
- hard coded to use https://api.psiturk.org since it is fairly stable now
updates to configuration options
first attempt at handling user-agent strings in more advanced ways

- no longer simply allow/deny "IE".  instead you provide strings and key terms that include entire classes of browsers

- quick docs:

special terms:
"mobile" - denies anything we thing might be a mobile browser
"tablet" - denies anything we think might be a tablet
"touchcapable" - denies anything we think might be touch
"pc" - denies any regular computer (not wise)
"bot" - denies anything that appears to be a bot/spider (not reliable since can be faked)

also any other stuff can match via string matching  For example "MSIE" or "America Online Browser" (see a partial list of user-agent strings here: http://www.useragentstring.com/pages/Browserlist/).  this IS case sensitive currently

the definition goes in new "browser_exclude_rule" config option
add separate global/local configuration

Config now separated into global and local files, with local options
overriding global.
Finish implementing new config structure

- default global and local config files live in psiturk/default_configs.
- when creating a new config file (e.g., when setting up example), file
  is just copied over from this folder.
- when loading config, defaults are also loaded, so any field missing
  from the user's config files will have the default value (this lets us
  add new config options without breaking psiturk for everyone).
- by default there are only a few fields in the global config, but
  advanced users could move some options out of the local config and
  into global, or vice versa.
Merge branch 'dev' into psiturk-org-services

Conflicts:
	setup.py
add some comments to PsiturkConfig

Might not be clear why things work the way they do otherwise...
Revert "Switch dependency to gnureadline to avoid the whole module name issue"

This reverts commit aa772aecf2dc27ea8fbd88fa5929d3823a08ace3.

Conflicts:
	setup.py
Add warning if user is using libedit readline

Switching to gnureadline was too good to be true. Underlying cmd/cmd2
classes import regular old readline, so without going in and editing
those and shipping our own version with psiturk we're stuck using a
module with the name readline.
these come from command line now
fixes issue with duration

- @alexanderrich - this works for me, let me know if it works for you
Merge remote-tracking branch 'origin/psiturk-org-services' into dev

Conflicts:
	psiturk/psiturk_config.py
	psiturk/psiturk_org_services.py
	psiturk/psiturk_shell.py