resolver: don't log hash collision incidents

The log message is quite CPU-intensive to generate, and some data sets
have enough hash collisions to throw off benchmarks.

Keep the event counter but drop the log message.

Signed-off-by: Zygo Blaxell <bees@furryterror.org>

src/bees-resolve.cc

@@ -161,9 +161,11 @@ BeesResolver::adjust_offset(const BeesFileRange &haystack, const BeesBlockData &
 
 	// Found the hash but not the data.  Yay!
 	m_found_hash = true;
+#if 0
 	BEESLOGINFO("HASH COLLISION\n"
 		<< "\tneedle " << needle << "\n"
 		<< "\tstraw " << straw);
+#endif
 	BEESCOUNT(hash_collision);
 
 	// Ran out of offsets to try