V2 Integration Test Issues

[goatgoose]

Problem:

The following issues were discovered when trying to run V2 tests with additional libcryptos in #3244. Any tests that were affected by these problems were temporarily disabled. When these issues are resolved, however, the tests that were disabled should be restored.

• improve local usability of integration tests #4342
• s2nc can't handshake with s2nd with awslc-fips #3247
• s2nc can't handshake with s2nd with openssl-1.0.2-fips #3248
• SSLyze scans fail with some libcryptos #3249
• Enable TLS 1.3 for libressl and boringssl libcryptos #3250
• Some V2 tests are flaky #3251
• OCSP validation not supported with boringssl libcrypto #3257
• pq_handshake V2 test unexpected cipher negotiated for PQ_TLS_1_0_2020_12 #3258
• s2n-tls fails to build with CMake with awslc/boringssl #3274
• ci: flaky well-known endpoints test #3999
• [AL2] Integrationv2 test_client_authentication failures #2399
• V2 Integration isssue on Arm/nix #4568

Solution:

For each issue, ensure that the behavior is not expected. If it isn't, fix the problem, and then enable testing support for the issue in V2.

• Does this change what S2N sends over the wire? If yes, explain.
• Does this change any public APIs? If yes, explain.
• Which versions of TLS will this impact?

Requirements / Acceptance Criteria:

All issues are addressed, either by finding issues to demonstrate expected behavior, or by resolving the problem in the issue and adding test support for the issue in V2.

• RFC links: Links to relevant RFC(s)
• Related Issues: Link any relevant issues
• Will the Usage Guide or other documentation need to be updated?
• Testing: How will this change be tested? Call out new integration tests, functional tests, or particularly interesting/important unit tests.
  • Will this change trigger SAW changes? Changes to the state machine, the s2n_handshake_io code that controls state transitions, the DRBG, or the corking/uncorking logic could trigger SAW failures.
  • Should this change be fuzz tested? Will it handle untrusted input? Create a separate issue to track the fuzzing work.

Out of scope:

N/A