OpenSSL 3.5 compatibility

[dcooper16]

Describe your changes

With the current master branch of OpenSSL (3.5.0-dev), the output that is provided by s_client has changed in the case of a cipher suite that uses an ephemeral key. Rather than preceding the ephemeral key information with "Server Temp Key: ", it is now preceded by either "Peer Temp Key:" or "Negotiated TLS1.3 group:". This PR modifies the lines that extract ephemeral key information from OpenSSL responses to accept any of these strings.

What is your pull request about?

• Bug fix
• Improvement
• New feature (adds functionality)
• Breaking change (bug fix, feature or improvement that would cause existing functionality to not work as expected)
• Typo fix
• Documentation update
• Update of other files

If it's a code change please check the boxes which are applicable

• For the main program: My edits contain no tabs and the indentation is five spaces
• I've read CONTRIBUTING.md and Coding_Convention.md
• I have tested this fix or improvement against >=2 hosts and I couldn't spot a problem
• I have tested this new feature against >=2 hosts which show this feature and >=2 host which does not (in order to avoid side effects) . I couldn't spot a problem
• For the new feature I have made corresponding changes to the documentation and / or to help()
• If it's a bigger change: I added myself to CREDITS.md (alphabetical order) and the change to CHANGELOG.md

[dcooper16]

OpenSSL 3.5 will have support for ML-KEM, ML-DSA, SLH-DSA, as well as support for using ML-KEM in key exchanges. testssl.sh can be enhanced to make use of this new functionality. I intend to work on that in one or more PRs, but this PR is just about ensuring that nothing that currently works breaks if OpenSSL 3.5 is used.

[drwetter]

Cool & thanks!