Add TLS 1.3 cipher-suite scanning using a capable OpenSSL

[SahandMas]

Summary

• detect whether the selected or system OpenSSL supports -tls1_3 and -ciphersuites;
• enumerate supported TLS 1.3 cipher suites in server-preference order;
• include TLS 1.3 suites in the existing terminal and JSON output; and
• make handshake benchmarking aware of TLS 1.3 cipher suites.

Approach

The bundled OpenSSL binaries remain unchanged for legacy protocol and cipher coverage. TLS 1.3 scanning uses the selected OpenSSL when it is capable, otherwise it falls back to a compatible system OpenSSL. If neither is available, CipherScan keeps the legacy scan results and emits a clear warning.

This keeps the patch focused on one file and avoids adding another binary to the repository.

Relation to existing work

This addresses #165. PR #169 proposed shipping OpenSSL 1.1.1 alongside a renamed legacy binary and included a larger refactor. This PR offers a smaller alternative that relies on an already-installed TLS 1.3-capable OpenSSL while preserving the current bundled binaries.

Validation

• bash -n cipherscan passes.
• TLS 1.3 scanning was manually validated before submission.