The error labels are at the top level of the response document, and the driver is assuming that they are embedded in the writeConcernError document. The fix is to ensure that error labels at the top level are properly added to MongoWriteConcernException.

Currently the code for this is not consolidated, but to avoid API changes in MongoWriteConcernException we won't centralize it there as part of this change.