In changing the pool's behavior to throw an error when it encounters a writeConcernError, we inadvertently broke some behavior for the bulk API that was already accommodating this case. We should modify our now-official MongoWriteConcernError to also include the full response, if ok: 1.

Additionally, our changes have broken expected user api for bulk. In this case, we need to explicitly catch MongoWriteConcernError}}s, and wrap them to look like they once did. Once this is complete, the tests in {{replset_operations_tests.js will pass.

NOTE: remember to reenable tests in replset_operations_tests.js when this work is complete