Allow a Proc to be used as an interaction_handler

[DamienRobert]

According to the doc one can pass a Hash or a Proc as a
:interaction_handler option, but only Hashes were wrapped into a
MappingInteractionHandler.

Fix this and add a test.

[capistrano-bot]

	1 Warning
⚠️	Please update CHANGELOG.md with a description of your changes. If this PR is not a user-facing change (e.g. just refactoring), you can disregard this.

Here's an example of a CHANGELOG.md entry (place it immediately under the * Your contribution here! line):

* [#436](https://github.com/capistrano/sshkit/pull/436): Command: wrap a Proc interaction_handler into a MappingInteractionHandler - [@DamienRobert](https://github.com/DamienRobert)

Generated by 🚫 Danger

[DamienRobert]

Ping? I did not add a changelog entry, but they are not in CHANGELOG.md anymore, so I don't know how to do it. Thanks!

[leehambley]

Hi Damien, We recently removed the changelog, and the contents of the release notes are managed with GitHub Actions since Matt's contribution in #472 - It's pretty neat. Are you interested in adapting your PR to meet those new "standards" so we can generate the release notes automatically. Cheers! Lee Hambley http://lee.hambley.name/ +49 (0) 170 298 5667

…

On Fri, 21 Feb 2020 at 22:36, Damien Robert ***@***.***> wrote: Ping? I did not add a changelog entry, but they are not in CHANGELOG.md anymore, so I don't know how to do it. Thanks! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#436?email_source=notifications&email_token=AAAEUCHJ4PNARO4V2FE77ZTREBCORA5CNFSM4FMIIHTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMUFIAA#issuecomment-589845504>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAEUCBFBGK2YZGRSRQMZH3REBCORANCNFSM4FMIIHTA> .

[DamienRobert]

Hi Lee,
yes I am interested to meet those new "standards", but I am not sure what I should do?

Should I resend this PR with a 'PR: Bug Fix' title? I looked at the logs of the project but I am not sure I understand how it works.

[mattbrictson]

Hi @DamienRobert , thanks for sticking with this PR. In terms of code quality and tests it looks good.

Each PR needs to have a label (that's the maintainer's responsibility) and a concise, descriptive PR title. The PR title is what gets included in the release notes. I'll tweak the title and then merge this in.

Thanks again for the PR and congrats on becoming a contributor to SSHKit!

[DamienRobert]

Ok, I see, thanks for editing the PR title and merging this!