Replace well_known_endpoints integration test with a hyper test

[goatgoose]

Problem:

The well_known_endpoints test performs TLS handshakes with a list of well-known endpoints, which ensures that the s2n-tls client remains compatible with well-known TLS servers.

However, this integration test is unique in that it doesn't require any of the other TLS providers. It just runs s2nc against all of the endpoints. A better place for this test might be s2n-tls-hyper, which would also allow for the s2n-tls hyper client to be tested against real endpoints over the network.

Solution:

Replace the well_known_endpoints integration test with an s2n-tls-hyper test.

Requirements / Acceptance Criteria:

What must a solution address in order to solve the problem? How do we know the solution is complete?

• 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:

Is there anything the solution will intentionally NOT address?