Upgrade: perl-Crypt-OpenSSL-RSA to version 0.33

[SumitJenaHCL]

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?
This PR is to upgrade the package perl-Crypt-OpenSSL-RSA to version 0.33

Change Log

• SPECS-EXTENDED/perl-Crypt-OpenSSL-RSA/perl-Crypt-OpenSSL-RSA.signatures.json
• SPECS-EXTENDED/perl-Crypt-OpenSSL-RSA/perl-Crypt-OpenSSL-RSA.spec
• cgmanifest.json

Does this affect the toolchain?

NO

Associated issues

• #xxxx

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-YYYY-XXXX

Test Methodology

• Local Build. (Needs to be build along with perl-Crypt-OpenSSL-Bignum, perl-Crypt-OpenSSL-Guess, perl-Crypt-OpenSSL-Random)
• Installation/Uninstallation verified on 3.0 container
  

[suresh-thelkar]

Code changes look good to me. Install/uninstall tests from the buddy build are failing. Can you please take a look.
If you have already verified them in a Azure Linux 3.0 container, please share the screenshot for the same.

[SumitJenaHCL]

Uploaded Screenshot verifying the installation/uninstallation of the package.

[cyberbandya007]

Buddy Build - https://dev.azure.com/mariner-org/mariner/_build/results?buildId=883954&view=results

[cyberbandya007]

Buddy Build have installation failures. @SumitJenaHCL , Can you check the installation of builts RPMs on local and update here.
Started new buddy build with required package during installation - https://dev.azure.com/mariner-org/mariner/_build/results?buildId=884120&view=results

[SumitJenaHCL]

Buddy Build have installation failures. @SumitJenaHCL , Can you check the installation of builts RPMs on local and update here. Started new buddy build with required package during installation - https://dev.azure.com/mariner-org/mariner/_build/results?buildId=884120&view=results

Installation test screenshot is attached above in the PR summary.

[cyberbandya007]

Buddy Build have installation failures. @SumitJenaHCL , Can you check the installation of builts RPMs on local and update here. Started new buddy build with required package during installation - https://dev.azure.com/mariner-org/mariner/_build/results?buildId=884120&view=results

Installation test screenshot is attached above in the PR summary.

That is from local build. I have specifically mentioned to download the built RPMs on local.