Investigate why Snappy upgrade from 1.1.1 to 1.1.6 regressed performance

We attempted to upgrade Snappy from 1.1.1 to 1.1.6 via MB-25339, as part of Vulcan. However this "upgraded" version resulted in various performance regressions (MB-26922, MB-26923, MB-26924), even though Snappy's own published numbers and our own micro-benchmarking runs the newer version was faster (up to 20% faster decompress, 5% faster compress; see https://github.com/google/snappy/releases/tag/1.1.4).

KV-Engine continues to spend a significant amount of time in snappy (de)compression; moreso for high DGM workloads (all data on-disk is Snappy-compressed), so it would be advantageous if we could take advantage of the performance improvements which should be available in newer versions. However we first need to understand why the last upgrade regressed.