tests 006.phpt and 007.phpt fail on multiple nodes owing to how they compare multi results

Currently, in tests 006 and 007, we rely on serialize of multiget responses to make a comparison. Since the results can be in a different order, this will frequently make tests fail.

For example, here's some dump output of v and keys in 006:

v is
string(414) "a:6:

{s:23:"couchbase_5025a95b7b7dd";s:29:"couchbase_value_5025a95b7b7e5";s:23:"couchbase_5025a95b7b7bc";s:29:"couchbase_value_5025a95b7b7c8";s:23:"couchbase_5025a95b7b7f2";s:29:"couchbase_value_5025a95b7b7f9";s:23:"couchbase_5025a95b7b801";s:29:"couchbase_value_5025a95b7b807";s:23:"couchbase_5025a95b7b81c";s:29:"couchbase_value_5025a95b7b823";s:23:"couchbase_5025a95b7b80f";s:29:"couchbase_value_5025a95b7b815";}

"
keys is
string(414) "a:6:

{s:23:"couchbase_5025a95b7b7bc";s:29:"couchbase_value_5025a95b7b7c8";s:23:"couchbase_5025a95b7b7dd";s:29:"couchbase_value_5025a95b7b7e5";s:23:"couchbase_5025a95b7b7f2";s:29:"couchbase_value_5025a95b7b7f9";s:23:"couchbase_5025a95b7b801";s:29:"couchbase_value_5025a95b7b807";s:23:"couchbase_5025a95b7b80f";s:29:"couchbase_value_5025a95b7b815";s:23:"couchbase_5025a95b7b81c";s:29:"couchbase_value_5025a95b7b823";}

"

Note that the same stuff is there, it's just not in the same order. In a single node cluster, it comes back in the same order but the results race for position in a multi-node cluster.