Upgrade: trilead-ssh2 version to 217.371.vc1d30dc5a_b_32

[BinduSri-6522866]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

What does the PR accomplish, why was it needed?
Upgrade: trilead-ssh2 version to 217.371.vc1d30dc5a_b_32

Build/Dependency Information

Please build the following packages with trilead-ssh2:
"jbcrypt ed25519-java"

Change Log

• modified: ../LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md
• modified: ../LICENSES-AND-NOTICES/SPECS/data/licenses.json
• new file: ../SPECS-EXTENDED/ed25519-java/0001-EdDSAEngine.initVerify-Handle-any-non-EdDSAPublicKey.patch
• new file: ../SPECS-EXTENDED/ed25519-java/0002-Disable-test-that-relies-on-internal-sun-JDK-classes.patch
• new file: ../SPECS-EXTENDED/ed25519-java/ed25519-java-CVE-2020-36843.patch
• new file: ../SPECS-EXTENDED/ed25519-java/ed25519-java-build.xml
• new file: ../SPECS-EXTENDED/ed25519-java/ed25519-java.signatures.json
• new file: ../SPECS-EXTENDED/ed25519-java/ed25519-java.spec
• new file: ../SPECS-EXTENDED/jbcrypt/jbcrypt-1.0.2.pom
• new file: ../SPECS-EXTENDED/jbcrypt/jbcrypt-build.xml
• new file: ../SPECS-EXTENDED/jbcrypt/jbcrypt.signatures.json
• new file: ../SPECS-EXTENDED/jbcrypt/jbcrypt.spec
• new file: ../SPECS-EXTENDED/trilead-ssh2/0001-Remove-the-dependency-on-google-tink.patch
• new file: ../SPECS-EXTENDED/trilead-ssh2/trilead-ssh2-build.xml
• modified: ../SPECS-EXTENDED/trilead-ssh2/trilead-ssh2.signatures.json
• modified: ../SPECS-EXTENDED/trilead-ssh2/trilead-ssh2.spec
• modified: ../cgmanifest.json

Does this affect the toolchain?

NO

Test Methodology

• Local Build:
  trilead-ssh2-217.371.vc1d30dc5a_b_32-1.azl3.src.rpm.log

• Installation check:

[sandeepkarambelkar]

Why can't we use autosetup here?

[BinduSri-6522866]

Updated.