Terminal Readline Commands are intercepted

[Nuru]

Describe the bug
Terminal Readline Commands are intercepted by Lens as Lens commands rather than being passed to Readline.

When exec-ing into a pod and getting a bash shell, bash provides Readline Commands bound to non-printing characters for editing the command line. While Lens' input focus is a terminal, non-printing characters should be sent to the terminal, not intercepted by Lens.

Note: this is separate from:

• kubectl exec buffers the first ctrl-p until the next character is typed
• Default tty binding of ctrl-s to (flow-control) stop interferes with Readline Command binding of forward-search-history to ctrl-s

To Reproduce
Steps to reproduce the behavior:

1. In Lens, select the Pods display from the sidebar and use Lens to open a shell in a pod that has bash installed
2. At the shell prompt (in the pod shell) type 'abcd' (do not type return) and note the cursor is after the 'd'
3. Type ctrl-a and note the cursor moved to before the 'a'
4. Type ctrl-f and note the cursor moved forward to between the 'a' and 'b', which is correct and expected, but the input focus has shifted from the terminal command line to the search box in the upper right of the UI window, which is wrong.
5. Type 'x' and note it appears in the search box, not on the command line

Expected behavior
While the input focus is in the pod shell window, keyboard input that generates a character should be sent to the pod shell and not intercepted or interpreted by Lens.

Environment (please complete the following information):

• Lens Version: 4.0.8
• OS: macOS X 10.15.7

[Nokel81]

Note: the shortcut key code is in src/renderer/components/input/search-input.tsx.