Should those server utilities be public in the first place?

@Andy-MS toSortedArray, enumerateInsertsAndDeletes, insertSorted, and removeSorted are public. Given that we require SortedArray<T> and SortedReadonlyArray<T> in a few places on the server, I'd say they're required.

combineProjectOutput should probably also be using Comparer<T>, rather than what it currently is.

I don't think there's a need to allow third-parties to call those, so they could be made internal. @sheetalkamat might be able to confirm.

@Andy-MS @chuckjaz Added the enumerateInsertsAndDeletes function in #15308, and you factored insertSorted and removeSorted out of inline-in-the-builder into utilities. So what was his and your intent? And combineProjectOutput has been public for a year, so if that were to be moved to use the Comparer<T> type, it would definitely need to be public.

Considering these are helpers for working with SortedArrays, which are on our public interface, I think these can stay public, and the enum and type alias supporting them can be made public, too.

I didn't have any intents with regards to public APIs since I didn't realize I was changing them. It doesn't sound like removeSorted should be a public API since it's just an implementation detail.

I agree with @Andy-MS as to not have these server utility functions public but to have them as internal instead.

@Andy-MS @sheetalkamat done. I've moved the offending types into an internal half of the namespace.