When we create a reply message for dbCheck command, we should serialize the nss according to the inputs of command request, eg, the "$tenant" and the "expectPrefix" fields, which comes from unparsed OpMsgRequest and is thread through request's serialization context to the code places where we create the reply message.

Today, the DbCheck is a BasicCommand which cannot access the unparsed request. We cannot serialize the nss correctly in reply message. 

In this ticket, we should amke the dbCheck command to be able to create the serialization context when parsing request and use the context when creating reply message.