perf: Integrate unit and spec benchmarking in js-libp2p CI

discussed in https://pl-strflt.notion.site/js-libp2p-perf-benchmarking-f7c42f96cbd44799a321347f6c15c8d4?pvs=4

Goals

• We would like to be able to benchmark js-libp2p across releases and compare performance, particularly across different permutations in the stack.
  • Testing different transports against each other performance wise.
• We are currently having an issue with performance with [Yamux performance](https://github.com/ChainSafe/js-libp2p-yamux/issues/42) and we would like to be able to nail down why there are such drastic differences.
• We have issues [sending large files](https://github.com/libp2p/js-libp2p/actions/runs/6265587906/job/17014869561?pr=2048#step:5:2415) and whilst this is cause by separate issue it would be beneficial to measure file transfer performance and have that running on CI.

### Tasks
- [ ] https://github.com/libp2p/js-libp2p/issues/1964
- [ ] https://github.com/libp2p/js-libp2p/issues/2120
- [ ] https://github.com/libp2p/test-plans/issues/307

Start with the linked Notion discussion and the task-list issues 1964, 2120, and test-plans#307 to establish the intended benchmark scope. Done should mean js-libp2p CI measures unit and spec performance across releases and stack permutations, including transport comparisons and file-transfer performance.