Feature: Settable "keyboard.chords.mode"

<h1 align=center><img alt="consequential inaccessibility ≠ incidental feature request" src="https://upload.wikimedia.org/wikipedia/commons/3/3b/Antu-preferences-desktop-accessibility-32.svg" height=48 /></h1> <details><summary align=center><b><code>Explainer</code></b></summary> --- **Note** — The following was added after reopening the issue… please read to understand my perspective when I opened this issue a while back. > TL;DR; > > This issue for folks like myself comes with accessibility related burdens that extend far beyond feeling 😯 because you triggered the wrong thing… For every unexpected outcome, there is a long period of observing to look for what makes it happen, then you need to figure out where to look for possible causes, then you find that, then you look for ways to fix it, creating all sorts of noise and all sorts of visual and cognitive burdens. > > So you get the gist, I am disabled my way, it never got in my way, but your chords feature is an actual disability not of my way, it is in my way! > > And so yes all that just because of a shortcut, yes, that is what others don't get to see — which is a good thing, but not accepting that some suffer this is hardly a fair thing to do just because there is more who don't need bother… please ❤️ > > DR; > > consequential inaccessibility ≠ incidental feature request </details> --- **Proposal** I'd like to propose a solution that will allow everyone to decide the degree of complexity they are comfortable with, without the need for any complicated configuration and possible very little change to the existing system. The user simply decides which "keyboard.chords.mode" they want to use in the `settings.json`, which will augment how VS code behaves immediately after the first key of a possible chord is pressed. <details><summary>This was in the original issue, it is not meant as a "feature request" merely my naïve way to try to "offer solutions" not "problems" but I realize now my mistake…</summary><p> > Let's…