[JENKINS-47458] update trilead-ssh2 version

[kuisathaverat]

See :

• JENKINS-47458 Check for null in Connection#getReasonClosedCause().
• JENKINS-47603 Just print the SCP response code under failure.
• JENKINS-55133 Support OpenSSH keys with AES256-CTR encryption.
• JENKINS-47603 wait for a timeout time if the packets have 0 size
• JENKINS-53653 assign the value on the else clause

This PR update the trilead-ssh2 due to a couple of bug fixed and a new encryption type supported

Proposed changelog entries

• Check for null in Connection#getReasonClosedCause().
• Print the SCP response code under failure..
• Support OpenSSH keys with AES256-CTR encryption.
• Wait for a timeout time if the packets have 0 size
• Ensure logger is assigned.

Submitter checklist

• JIRA issue is well described
• Changelog entry appropriate for the audience affected by the change (users or developer, depending on the change). Examples
  * Use the Internal: prefix if the change has no user-visible impact (API, test frameworks, etc.)
• Appropriate autotests or explanation to why this change has no tests
• For dependency updates: links to external changelogs and, if possible, full diffs

Relevant PRs

• [JENKINS-47458] - Check for null in Connection#getReasonClosedCause() trilead-ssh2#25
• [JENKINS-47603] Just print the SCP response code under failure trilead-ssh2#26
• [JENKINS-53651] wait for a timeout time if the packets have 0 size trilead-ssh2#28
• Support OpenSSH keys with AES256-CTR encryption trilead-ssh2#32

@oleg-nenashev @MarkEWaite

[MarkEWaite]

I confirmed with the build from the CI job that an ed25519 private key generated on Debian Buster is correctly used as an agent. Thanks for doing this!

[batmat]

FTR diff is jenkinsci/trilead-ssh2@trilead-ssh2-build-217-jenkins-11...trilead-ssh2-build-217-jenkins-14

[TobiX]

FTR, "Support OpenSSH keys with AES256-CTR encryption." mentions the wrong ticket. The correct one is JENKINS-55133