Consider forking/merging strategy for BoringSSL test runner

[blakebyrnes]

BoringSSL has a fork of golang's tls implementation as well that it uses as a runner for it's test suite. There are a number of potential holes in uTls that could be plugged with implementations already written in this wrapper (certificate compression, channel ids, upcoming quic, etc). I'm still trying to understand exactly how this could work (still poking through utls to understand it), but it seems like a promising option to keep in sync as tls signatures change.

[blakebyrnes]

https://github.com/google/boringssl/tree/f9cc26f9c1c07668e29be71e08324f68d50d0942/ssl/test/runner

[sergeyfrolov]

BoringSSL test runner does seem like a useful addition to uTLS.