chore: Check whether test failures are caused by port exhaustion

[bthomee]

High Level Overview of Change

This change adds an extra step to the CI test job that outputs network info.

Context of Change

We suspect random test failures are being caused by port exhaustion on the GitHub runners when many jobs are being run at the same time.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Refactor (non-breaking change that only restructures code)
• Performance (increase or change in throughput and/or latency)
• Tests (you added tests for code that already exists, or your new feature included in this PR)
• Documentation update
• Chore (no impact to binary, e.g. .gitignore, formatting, dropping support for older tooling)
• Release

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.3%. Comparing base (efd4c1b) to head (5a61044).
⚠️ Report is 1 commits behind head on develop.

Additional details and impacted files

@@           Coverage Diff           @@
##           develop   #5938   +/-   ##
=======================================
  Coverage     78.3%   78.3%           
=======================================
  Files          817     817           
  Lines        68944   68944           
  Branches      8304    8296    -8     
=======================================
+ Hits         53993   54003   +10     
+ Misses       14951   14941   -10     

see 7 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[ximinez]

What can go wrong? The job has already failed at this point...