sync: update CI config files

[web3-bot]

Syncing to commit protocol/.github@137ffc6.

[Stebalien]

@marten-seemann the error here appears to be an actual bug somewhere adjacent to the connection gater. It looks like this may be failing in QUIC, but it could also be more generalized.

[marten-seemann]

@Stebalien will investigate

[marten-seemann]

@Stebalien Indeed, this is because in QUIC, we don't distinguish between InterceptAccept and InterceptSecured: https://github.com/libp2p/go-libp2p-quic-transport/blob/6f581f3da03a00073b292098e7b7259fd072ee00/listener.go#L73-L76
In both cases, we only check the connection gater after handshake completion. When implementing this, we had the following 3 options:

1. Drop packets from the blacklisted mutliaddr before they even reach quic-go.
2. Send a CONNECTION_CLOSE with a "you've been blacklisted" error code before starting the handshake (see add a callback to allow filtering of incoming connections by IP address quic-go/quic-go#2558).
3. Complete the handshake and then reject the connection.

We decided for 3. because:

• Option 1 makes the peer run into a handshake timeout (5s), which is not a very friendly thing to do
• Option 2 is an unauthenticated signal, and could be used by an attacker to prevent two peers from connecting to each other for an extended period of time

How should we proceed here? Should we disable this test case when using QUIC (and, in general, be explicit which transport we run the connection gater tests on)?

[Stebalien]

Yeah, I think it's reasonable to disable (or limit) these tests on QUIC. This should also fix #251.