Added signature benchmarks

[jackctj117]

Added BC, wolfJCE and Sun signature algorithms benchmarks as well as refactored other test to better insert security providers to avoid provider conflicts.

[Copilot]

Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (2)

examples/provider/CryptoBenchmark.java:725

• Reassigning providerName when using the SunJCE branch changes its identity for later logging; consider using a separate variable (e.g., actualProviderName) to retain the original provider identity for clarity.

providerName = "SunRsaSign";

examples/provider/CryptoBenchmark.java:737

• [nitpick] The EC curve name 'secp256r1' is repeated; consider extracting it into a constant to improve maintainability.

keyGen.initialize(new ECGenParameterSpec("secp256r1"));

[cconlon]

I don't understand why we can't include SUN/Oracle Signature benchmarks. As long as we are calling public Java Security API's, doing something like Signature.getInstance("SHA256withRSA", "SunRsaSign"); shouldn't cause any problems that I am aware of.

The list of Oracle security providers and the services they offer for Java 11 (for example) can be found here: https://docs.oracle.com/en/java/javase/11/security/oracle-providers.html.

[Copilot]

Pull Request Overview

This PR adds signature performance benchmarks for BC, wolfJCE, and Sun providers and refactors provider setup to avoid conflicts across tests.

• Introduces SIGNATURE_ALGORITHMS and SUN_SIGNATURE_ALGORITHMS arrays and a new runSignatureBenchmark method
• Consolidates provider insertion/removal into setupProvidersForTest and adds setupDigestProvider
• Updates main to invoke signature benchmarks and cleans up table formatting and exception handling

[cconlon]

See new Copilot suggestions

[cconlon]

When I run the benchmark with Java 23, I get this error:

Running crypto benchmark with Bouncy Castle (version 1.80)
Exception in thread "main" java.lang.IllegalAccessError: class CryptoBenchmark (in unnamed module @0x64485a47) cannot access class com.sun.crypto.provider.SunJCE (in module java.base) because module java.base does not export com.sun.crypto.provider to unnamed module @0x64485a47
	at CryptoBenchmark.main(CryptoBenchmark.java:930)
../../../lib/bcprov-jdk18on-1.80.jar	../../../lib/bctls-jdk18on-1.80.jar

ChatGPT thinks the SunEC provider is already registered on all versions of Java, and we don't need to instantiate it ourselves (https://chatgpt.com/share/683f8cfa-5d80-8000-8648-a8fbaeca3cb3). Can you try to adjust so we can maintain compatibility with running on newer Java versions?

[Copilot]

Pull Request Overview

This PR adds new signature benchmarks for BC, wolfJCE, and Sun signature algorithms and refactors test setup to avoid provider conflicts. Key changes include:

• Introduction of a runSignatureBenchmark method and supporting helper methods for signature algorithm detection and execution.
• Refactoring of provider setup across different benchmark sections to ensure a clean environment.
• Minor formatting updates in benchmark output displays.