fix: enable inputpane virtual keyboard by default

[nornagon]

Description of Change

First commit here is just running git-import-patches followed by git-export-patches. The second commit backports https://chromium-review.googlesource.com/c/chromium/src/+/946928 to enable the inputpane virtual keyboard by default, which should fix some scenarios in Windows 10 RS4 and later in which the virtual keyboard wasn't showing when it should have.

Checklist

• PR description included and stakeholders cc'd
• npm test passes
• tests are changed or added
• PR title follows semantic commit guidelines
• PR release notes describe the change in a way relevant to app developers, and are capitalized, punctuated, and past tense.

Release Notes

Notes: Fixed an issue on Windows 10 RS4 and later that was causing the virtual keyboard not to appear when focusing some input fields.

[deepak1556]

LGTM, any reason patch was preferred over passing it to --enable-features ?

[nornagon]

I prefer the backport because:

1. it'll disappear automatically when rebasing (though i suppose in this case, since it's already gone on master, this isn't really an advantage)
2. it's nice to have a direct backport of code that i know is in chrome
3. this allows disabling the feature with --disable-features rather than forcing it
4. i don't know where the "pass extra things to --enable-features" code in Electron is 😅

[deepak1556]

1 and 2 are compelling reasons to have this as a patch :)

Regarding 4 , they are in AtomBrowserMainParts::InitializeFeatureList

[release-clerk]

Release Notes Persisted

Fixed an issue on Windows 10 RS4 and later that was causing the virtual keyboard not to appear when focusing some input fields.