On non-sharded clusters, dropping a non-existent collection results in an error from the server. This error is inconsistent with behavior on sharded topology types and can be annoying for both users and driver developers alike. We should consider suppressing this error in the various drop operations.

This suppression is implemented in a few drivers already and appears to be a supported idea by the server team (see SERVER-43894).