Ensure s2n-tls and rustls agree on event order

[camshaft]

Problem:

Currently, s2n-tls and rustls emit the TLS events in a different order, which can cause issues for event subscribers expecting a certain order for both.

Currently the SNI and ALPN are in different orders:

https://docs.rs/s2n-quic/latest/s2n_quic/provider/event/trait.Subscriber.html#method.on_application_protocol_information
https://docs.rs/s2n-quic/latest/s2n_quic/provider/event/trait.Subscriber.html#method.on_server_name_information

Solution:

We should make sure the event order is the same between both. We should have tests in place showing that they are the same.