fix(ssh): read force keyboard-interactive as a boolean when resolving hosts (#1553)

The column holds the text "true"/"false", and the resolver passed it
through as-is. The string "false" is truthy, so the password provider
treated every saved host as forced keyboard-interactive and left the
password out. Jump hops are built straight from the resolved host, so a
password hop whose server doesn't offer keyboard-interactive failed with
"All configured authentication methods failed".

src/backend/hosts/host-resolver.ts

@@ -129,6 +129,10 @@ export async function resolveHostById(
     }
     host.terminalConfig = rest;
   }
+  // Stored as the text "true"/"false"; the string "false" is truthy and would
+  // make the password provider skip password auth.
+  host.forceKeyboardInteractive =
+    String(host.forceKeyboardInteractive) === "true";
   // A row the boot copy has not reached yet still has them in terminal_config.
   host.sshOptions = parseSshOptions(
     host.sshOptions != null ? host.sshOptions : host.terminalConfig,