split_buffer_common was entirely unused, and deque_base_common
was unused except for two calls to __throw_out_of_range(), which have
been inlined.
The usual intent of the __xxx_base_common base classes is to localize
where the exception-throwing code is instantiated, however that wasn't
the case here because we never explicitly instantiated those base classes
in the shared library, unlike what we do for basic_string and vector.
I notice these were never _LIBCPP_HIDE_FROM_ABI or whatever. But that's fine, right? I believe I agree that this PR doesn't cause an ABI break in any interesting sense.