Fix defragmenter MappedMemory test by increasing the fuzz_factor
Fix defragmenter MappedMemory test by increasing the fuzz_factor

Changes introduced by 883e90ca slightly increased our memory overhead
as StoredValueFactory is now built from an abstract base class
(adding vtable storage cost).

The reviewed commit didn't fail CV, but was committed via cherry-pick,
meaning it picked up a new parent. The combination of the new parent
and the change appears to have increased overhead enough to fail the
defragmenter test.

Change-Id: I2ec68dc5139e0f70ab68f15dc2db1490afcde832
Reviewed-on: http://review.couchbase.org/74910
Tested-by: Build Bot <80754af91bfb6d1073585b046fe0a474ce868509@couchbase.com>
Reviewed-by: Dave Rigby <a09264da4832c7ff1d3bf1608a19f4b870f93750@couchbase.com>

membase/ep-engine,couchbase/ep-engine,couchbase/ep-engine,couchbase/ep-engine,daverigby/kv_engine,membase/ep-engine,couchbase/ep-engine,membase/ep-engine,daverigby/kv_engine,daverigby/kv_engine,daverigby/kv_engine,membase/ep-engine