lock debug logging

Logging when lock is acquired and released to help in debugging AUTO-587
logging in silverberg itself

that is not yet merged in silverberg
scheduler lock debug logging

not sure if we need this
updated silverberg version to use BasicLock logging
debug logs logged at different level

Implemented a debug() method in BoundLog that maps to level=7 msg(). This is used to distinguish normal
logs from debug logs

Yet to add tests
using debug log in different places
create group policy validation bugfix

When multiple policies are sent in create group request, only first policy was getting validated but the whole
request was getting stored. When scheduler policy is processed it causes exception and 500 error.

Changed to validate all elements in the array. Please see
http://tools.ietf.org/html/draft-zyp-json-schema-03#section-5.5
Revert "debug logs logged at different level"

This reverts commit e4dc25c081a6896ecb234342a6ce2e96d18317b0.
added negative test - create group with multi policy invalid request
AUTO-539 Added group name to state dict
removed debug usage from some places

still incomplete. scheduler tests do not pass
Integration fix.
pulling from config rather than writing to schema
Had to fix JSON from Cassandra vs objects in tests for config
Fixed linting errors.
made some irritating mock logging changes
Merge branch 'master' into lock_logging

Conflicts:
	otter/scheduler.py
	otter/test/test_scheduler.py

occurred after klein change
included group name validation within theget group state test
lint fix
removed other references of debug