See if Test::Net::SSLeay could handle security changes done in OpenSSL 3.0 alpha 5

[h-vn]

Changes in #288 described in #287 added calls to two test files to set security level to 0 with OpenSSL 3.0.0 and later.

The affected tests require using TLSv1 and TLSv1.1, but our Test::Net::SSLeay did not detect that these versions were not usable. Apparently the reason is that while the TLS versions are permitted on security level 1, the usability test did not go far enough to discover that the ciphersuites are now too weak to actually connect anywhere.

Should Test::Net::SSLeay be updated or are the changes in tests good enough. Note that the tests should really run as long as the TLS versions < 1.2 are supported, even if this requires setting security level to 0.