Update connection settings when using a password to connect ssh

[soapy1]

When connecting over ssh using net-ssh use the non_interactive argument must be set when authenticating with a password.

The "keyboard-interactive" options may be used as a default auth method, like in the net-ssh defaults (ref: https://github.com/net-ssh/net-ssh/blob/8a176a6ea0db1b59a21834df806a257a0b76e943/lib/net/ssh/config.rb#L52)

fixes #13008

[legal90]

@chrisroberts @soapy1 Hi! This PR has is causing the unexpected behavior in vagrant-parallels provider. Our provider's method ssh_info returns nil at the early stage, when the VM has just started, but didn't receive its IP yet:

https://github.com/Parallels/vagrant-parallels/blob/93aac8af8c63820b6d67b4487413e78218b1caac/lib/vagrant-parallels/provider.rb#L66-L68

We expect that the next attempt in 1-2 seconds will be successful.
But after this PR it's asking for a password instead of retrying:

$ bundle exec vagrant up
Bringing machine 'default' up with 'parallels' provider...
==> default: Registering VM image from the base box 'test-centos'...
==> default: Creating new virtual machine as a linked clone of the box image...
==> default: Unregistering the box VM image...
==> default: Setting the default configuration for VM...
==> default: Setting the name of the VM: vagrant-parallels_default_1679487998890_21336
==> default: Preparing network interfaces based on configuration...
    default: Adapter 0: shared
==> default: Clearing any previously set network interfaces...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: :22
    default: SSH username: vagrant
    default: SSH auth method: private key
Password:

Is that the expected behavior now, so we should handle that properly on the parallels provider side? Or maybe we can just fix that here, in vagrant?

[chrisroberts]

@legal90 Hi! Sorry for the delay on circling back around to this. I'm walking through the behavior here and the behavior described in the original issue it was meant to address. The resulting behavior does not appear to be ideal and I'll be making some modifications that will be up in a new PR shortly.

[chrisroberts]

PR here: #13194