Trying to debug these tests in CI is incredibly difficult and since they depend on older versions of previously published modules, if something breaks due to a bug in released code it's very hard to fix it.
Instead follow the pattern in the perf tests and include the full test implementations here.
The test output can have occurrences of `{` that aren't the string we are looking for, eg:
```
dialer-1 | test browser
dialer-1 | [JavaScript Error: "Clear-Site-Data header found. Unknown value “"cache"”." {file: "http://127.0.0.1:34451/" line: 0}]
dialer-1 | [JavaScript Error: "Clear-Site-Data header forced the clean up of “cookies” data." {file: "http://127.0.0.1:34451/" line: 0}]
dialer-1 | [JavaScript Error: "Clear-Site-Data header forced the clean up of “storage” data." {file: "http://127.0.0.1:34451/" line: 0}]
```
These fail to parse so improve the results parsing by:
1. Try parsing every instance of `{...}` in the output, not just the first
2. Test the output for the `handshakePlusOneRTTMillis` and `pingRTTMilllis` keys
* feat: add new implementation versions (go)
* ci: generalise adding new implementation versions
* ci: automate new version addition for rust-libp2p and js-libp2p
github-actions[bot]
Alex Potsides
Marco Munizaga
Piotr Galar
Sukun
diegomrsantos
Thomas Eizinger
Chad Nehemiah
kevodwyer