It will be necessary for tests to detect if the current storage engine supports KV drop-pending idents and adapt the expected behavior accordingly. One possible solution would be to add a field to the storageEngine subsection of the db.serverStatus() output as follows:

storageEngine: {
	"name" : "wiredTiger",
	"supportsCommittedReads" : true,
	"supportsPendingDrops" : true,       //  <<<----- ADD THIS FIELD
	"supportsSnapshotReadConcern" : true,
	"readOnly" : false,
	"persistent" : true
}