fix(ssh-tunnel): update fields for open tunnel with private + private key passwords

[hughhhh]

SUMMARY

With the new extensions class, we forgot to update the params to match the ssh_tunnel.open_tunnel function.
private_key -> ssh_pkey
ssh_private_key -> ssh_private_key_password

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

• Has associated issue:
• Required feature flags:
• Changes UI
• Includes DB Migration (follow approval process in SIP-59)
  • Migration is atomic, supports rollback & is backwards-compatible
  • Confirm DB migration upgrade and downgrade tested
  • Runtime estimates and downtime expectations provided
• Introduces new feature or API
• Removes existing feature or API

[codecov]

Codecov Report

Merging #22764 (7cec6a2) into master (0870a0b) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##           master   #22764   +/-   ##
=======================================
  Coverage   67.25%   67.25%           
=======================================
  Files        1876     1876           
  Lines       71819    71819           
  Branches     7864     7864           
=======================================
  Hits        48299    48299           
  Misses      21494    21494           
  Partials     2026     2026           

Flag	Coverage Δ
hive	52.59% <0.00%> (ø)
javascript	53.73% <ø> (ø)
mysql	78.57% <0.00%> (ø)
postgres	78.64% <0.00%> (ø)
presto	52.49% <0.00%> (ø)
python	81.88% <0.00%> (ø)
sqlite	77.00% <0.00%> (ø)
unit	51.53% <0.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
superset/extensions/ssh.py	64.10% <0.00%> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[Antonio-RiveroMartnez]

Oh! I was reading the docs here: https://sshtunnel.readthedocs.io/en/latest/ thanks!
Also, not a blocker for these changes, but probably worth mentioning we should make sure that when updating a tunnel, if we send a password or private_key/private_key_password, we remove the other login method from the tunnel (the UI is doing it already), otherwise, it will get into the if all the time if both are present, even if password is not the latest login method of the tunnel.

[hughhhh]

Let's cut a ticket for this as well on our end

[Antonio-RiveroMartnez]

LGTM!