Wildcard expansion blocks normal completion

[Mahmoud Al-Qudsi]

I found a case where the recent wildcard/variable expansion feature blocks a regular completion from being suggested. At least in my case, I wanted the completion and not the expansion.

Directory contains multiple files with extension .abc and .abc.ext and I wanted to autocomplete rm *.abc.ext so I typed in rm *.abc<TAB> and instead of getting *.abc.ext as a completion, the *.abc was expanded to the matching files.

IIRC, when this feature was landed we did not want it to suppress any completions and intended it to be unambiguously the fallback UX. I'm not sure how to resolve this so we can have both completions and/or expansion in this specific case, but my preference would be that if we have to choose one it is completions.