CMSItems

Adds a `CMSItems[K]` implementation of `CMS[K]` which, like `CMSItem[K]`, is exact, but for a small set of keys instead of just one.

You can add `CMSItem` and `CMSItem` or `CMSItems` and `CMSItems` and get a `CMSItems`. At a certain threshold (currently set to 100 items), this will transition to a `CMSInstance[K]`.

I haven't updated the TopN or TopPct variants, just the basic CMS.

I have a specific need for this, but it seems like a generally useful optimization. It could *probably* entirely replace `CMSItem` but I wouldn't want to do that without benchmarking first, which I have not done.

Thoughts @johnynek @miguno?
When `maxExactCount == 0` what should happen to this `case`?  That is, when it is zero my understanding is that the user wants to disable the exact counting optimization based on `CMSItems`, so this `case` statement should rather be "if (zero) oldCode else newCode" I think.

That being said, it looks to me as if we'd have to thread such if-else switches for maxExactCount through multiple parts of the CMS code, which is an indication that there might be a better pattern to enable/disable the new optimization functionality?