[extension/healthcheckv2extension]: Report for failed tests on main

[github-actions]

Auto-generated report for __run_3 job build.

Link to failed build: https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/16757095458

Test Failures

• TestComponentStatus

=== RUN   TestComponentStatus
    extension_test.go:42: 
        	Error Trace:	/home/runner/work/opentelemetry-collector-contrib/opentelemetry-collector-contrib/extension/healthcheckv2extension/extension_test.go:42
        	Error:      	Received unexpected error:
        	            	failed to bind to address 127.0.0.1:43857: listen tcp 127.0.0.1:43857: bind: address already in use
        	Test:       	TestComponentStatus
--- FAIL: TestComponentStatus (0.00s)

Note: Information about any subsequent build failures that happen while
this issue is open, will be added as comments with more information to this issue.

[github-actions]

Pinging code owners for extension/healthcheckv2: @mwear @evan-bradley. See Adding Labels via Comments if you do not have permissions to add labels yourself. For example, comment '/label priority:p2 -needs-triaged' to set the priority and remove the needs-triaged label.

[evan-bradley]

I feel a little stumped by this one. The failing test uses testutil.GetAvailableLocalAddress to get the port, which is run only 9-10 lines of code above the failed line. I suspect this is because there was a contention with some other test that was running in parallel, but I'm not sure how to solve that without retries or a coordinating layer between all of our tests.