scheduler consistency is QUORUM

It is possible that 1 api node deletes event and before it gets propogated to other cass nodes, other
api node picks the same event causing the same policy to get executed twice. So, read and writing at
quorum that guarantees consistency. The slower performance due to this is not really a concern since it
is happening in background.
using get_consistency_level instead of hard-coding
added tests for get_consistency_level
pep8 fix
using if instead - per @dreid
Logging improvements

- bind_log decorator to bind kwargs to log
- CannotExecutePolicyError logged as msg: TBD fully
all rest methods kwargs changed to undersore names

to have logs consistent with rest of the system
Also, having bind_log but using it internally in with_transaction_id
reverted ignoring CannotExecutePolicyError change
reverting ignore exception changes
seperate method to ignore exceptions

this commit has part of change made in better_logging branch. Need to extract other parts and put it
this branch
Adding ignore_and_log from better_logs branch

Made changes to test to reflect code changes
pep8 fix
Updated max entities to 1000
incomplete - started tests
scheduler exec policy logging test added
pep8 fixes
support other regions
added test to check if bind_log from with_trans_id works
Merge branch 'master' into better_logs
changed test to reflect bind changes