Add conformance tests for connect-node

[srikrsna-buf]

Add connect-node-conformance package with server implementation. Based on the reference server implementation.

Tested with the following conformance config:

features:
  versions:
    - HTTP_VERSION_1
    - HTTP_VERSION_2
  protocols:
    - PROTOCOL_CONNECT
    - PROTOCOL_GRPC
    - PROTOCOL_GRPC_WEB
  codecs:
    - CODEC_PROTO
    - CODEC_JSON
  compressions:
    - COMPRESSION_IDENTITY
    - COMPRESSION_GZIP
    - COMPRESSION_BR
  supportsTls: true
  supportsTlsClientCerts: true
  supportsConnectGet: true
  supportsHalfDuplexBidiOverHttp1: true
  requiresConnectVersionHeader: false
  supportsMessageReceiveLimit: true

[timostamm]

I did not take a close look at the server implementation, but this looks solid 👍

Left one comment about error detail debug values.

The readme for this new package needs more details, and the test run need to be wired up in make. I guess it only makes sense to do that after conformance v1 has been released.

The old crosstests need to be removed from this repo. I guess this is only feasible after #890 (we'll also want to run a Node fetch client, a browser fetch client, and at least retain the browserstack tests).

[timostamm]

Still looking solid to me 🙂 Would be great to have one of the conformance authors take a look, though.

Doesn't seem great to merge before conformance is released. What's your take?

[srikrsna-buf]

Still looking solid to me 🙂 Would be great to have one of the conformance authors take a look, though.

Doesn't seem great to merge before conformance is released. What's your take?

Agree on conformance authors taking a look, about merging before v1 we are only merging to a branch so that I can continue to work on other environments

[srikrsna-buf]

@timostamm @smaye81 Added the test to CI. This is now good to go

[timostamm]

Would be nice to remove the dep on fflate as noted in #886 (comment).

LGTM from me, but let's have @smaye81 take a look.

[smaye81]

Sorry for the delay @srikrsna-buf. Left some comments.

[smaye81]

Minor nits that can help clean this up:

• You can omit protocols and codecs since all options are supported (if absent, all are assumed)
• You can also omit supportsTls, supportsConnectGet, requiresConnectVersionHeader, and supportsMessageReceiveLimit since you have them listed as the defaults and if absent, the defaults are assumed.

[srikrsna-buf]

I did think of omitting the defaults but it just felt easier to parse and see what is included just by looking at the config. I'll omit them in a separate PR.