Clean up Manager constructor (still in discussion)
Make exceptions more verbose
Delete commented code
Stub out AllDocsMode
Stub out getConflictingRevisions()
stub out saveAllowingConflict()
Throw IOException since Manager ctor now throws an IOException
update testConflict() to call the newly added stubbed out methods.  test currently fails.
Implement saveAllowingConflict(), testConflict() is now one step closer to passing.
Modify Database.getAllDocs to consider the QueryOptions.allDocsMode and act according to spec.  testConflict() test now gets further.
getConflictingRevisions() implemented.  not tested.
Default the allDocsMode to ALL_DOCS.  Not sure if this was causing any issue.
testAllDocs() test was failing before this fix.  A recent commit broke it, was calling cursor.moveToNext() too many times.
Fix major bug in conflict handling.  testConflict() gets further, but not quite passing yet.

saw testConflict() fail with
        junit.framework.AssertionFailedError: expected:<{dc5e182f-f64e-4d2a-b642-dbe6e1a90ea1 #2-367d8e53-96a9-4475-8457-60b92405e7ff}> but was:<{dc5e182f-f64e-4d2a-b642-dbe6e1a90ea1 #2-84451ede-6a39-47f0-9934-5719bcc814e3}>
        at com.couchbase.lite.ApiTest.testConflict(ApiTest.java:435)
Remove debug statements from test
Some conflicts were not being added in the getAllDocs() query.  now testConflict() test completely passes.

 (other tests in suite are failing however due to previous changes)
Modify tests to expect _conflicts key in value in getAllDocs responses.  (tests are annoyingly brittle here)