lazily create merge files to avoid creation of empty files

[evanmcc]

in situations with few hot keys, you can produce a whole ton of empty data files. when all of keys in a partial merge have already expired, a data file will be created and nothing will ever be put into it. These files aren't cleaned up until reopen, so they can cause problems when may of them accumulate over time.

Moving to a lazy file creation strategy avoids this problem.

fixes #113

Testing notes:

See #116 for test setup.

The symptom here is a buildup of 0 length data files paired with empty 18 byte hint files. These should be readily apparent in the setup given above, they will begin to appear as soon as merges start, and will build up linearly over time. On an overnight run, tens of thousands can build up.

None should appear (except very briefly, as new files are started) with this patch applied.

[evanmcc]

Have done a little testing on this now. This does seem to avoid the tight put loop on small keysets case. Passes unit tests.

[slfritchie]

Hi, Evan. The code looks good, and all the tests (including the PULSE test) are happy. NOTE that the bitcask_qc_expiry test requires a commit that I put onto 'develop' earlier today. +1, thanks!