Inconsistencies with Trigger (full) completions when (incomplete) completions are already active

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ --> <!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ --> <!-- Please search existing issues to avoid creating duplicates. --> <!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: https://code.visualstudio.com/insiders/ --> <!-- Use Help > Report Issue to prefill these. --> - VSCode Version: 1.49.3 - OS Version: 10.15.7 @jrieken This is a follow up to https://github.com/microsoft/vscode/issues/99504. The issue is fixed in some instances, but not in others. Here's an example with a Go file where I have space enabled as a trigger char and then retype the line with space disabled as a trigger character.  Previously, upon typing `return n`, only Kite's completions would display. This has since been fixed via #99504. But, you can see in the gif that `return nil, e` results in Intellisense completions being suppressed, unless the trigger for space is turned off. Similarly for JS:  Previously, IntelliSense completions for `setAutoInstallPluginsEnabled: (e` were being suppressed. This has since been fixed. But, `setAutoInstallPluginsEnabled: (enabled) => dis` results in completions being suppressed. If I turn off space as a trigger, VSCode is able to suggest `dispatch` and `disabled`, as you can see at the end of the screen capture.