Adds a CodeCompleteOption to folds together compatible function/method overloads into a single item. This feels pretty good (for editors with signatureHelp support), but has limitations.
This happens in the code completion merge step, so there may be inconsistencies (e.g. if only one overload made it into the index result list, no folding).
We don't want to bundle together completions that have different side-effects (include insertion), because we can't constructo a coherent CompletionItem. This may be confusing for users, as the reason for non-bundling may not be immediately obvious. (Also, the implementation seems a little fragile)
Members never come from the index for completion, right? Maybe add an assert here instead?