Remove Primitive Optimization for Boolean Collections

[bmarcaur]

Before this PR

list<boolean> was optimized in this move to eclipse-collections, but its usage is almost non-existent (all instances appear to be some copy-paste from Excavator?). IMO, it's usage, or really this optimization, signals to devs that using a wire format of list<boolean> is a good idea, when a bit mask would be a much better abstraction for such a structure when it comes to our serialization.

On the other hand, it feels like an odd omission given the shape of the feature. Net net, I think removing it lowers our ownership overhead of this. boolean is a weird primitive type and when tackling changes for the 4 primitive types boolean is always a little unique. For example:

• When adding serialization optimizations it did not make sense to change the serializer because a bit is turned into the string literal false or true.
• Additionally, when trying to optimize the addAll paths for primitive arrays the boolean variant of the methods needed some different routines due to Arrays.stream not having a boolean variant.

After this PR

Treated like any old boxed type, in the long term we should consider a bit mask type for an efficient representation of the usage pattern.

Possible downsides?

This may regress the peak memory usage on the small use cases, but also let's consider leveraging more expressive external types to experiment.

[carterkozak]

lgtm, thanks!