Switch to MongoClient, and set an op_timeout.

I've seen occasional cases of MoSQL hanging after certain replset
reconfigurations. I suspect there's a mongo-ruby-driver bug I haven't
found yet, but for now, let's just set a long op timeout, and hope
that will kill us if this recurs.