Add expected failure test cases.

@Jorropo caught a bug in go-libp2p v0.24.0 where a node configured to use Noise could dial a node configured to use TLS (https://github.com/libp2p/go-libp2p/pull/1946)

In a subsequent pull request, we should extend the test cases in here to test the non happy-path (either as a part of the same github action as these or as a separate one that runs as a regression test in a nightly job.)

_Originally posted by @p-shahi in https://github.com/libp2p/test-plans/issues/85#issuecomment-1346056954_

Locate the existing interoperability test cases referred to as “these,” then read the linked go-libp2p pull request for the Noise-versus-TLS regression. Add expected-failure coverage for incompatible configurations and run the relevant GitHub Action or nightly regression job to verify the mismatch is detected.

Written by the indexing model from the issue text.