chore: reduce flakiness for test api equivalence spec

[CatalinSnyk]

Pull Request Submission Checklist

• Follows CONTRIBUTING guidelines
• Commit messages
  are release-note ready, emphasizing
  what was changed, not how.
• Includes detailed description of changes
• Contains risk assessment (Low | Medium | High)
• Highlights breaking API changes (if applicable)
• Links to automated tests covering new functionality
• Includes manual testing instructions (if necessary)
• Updates relevant GitBook documentation (PR link: ___)
• Includes product update to be announced in the next stable release notes

What does this PR do?

Swap out the "localhost" for the IPv4 address to reduce the flakiness for the test-api-equivalence acceptance tests.

Where should the reviewer start?

• test/jest/acceptance/snyk-test/unified-test-api-equivalence.spec.ts

How should this be manually tested?

• Wait for CI to pass - the changes should be aligned with some other acceptance tests that make use of this pattern.

What's the product update that needs to be communicated to CLI users?

N/A - CI fix only.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[PeterSchafer]

Question: why not exchange the deprecated method as well and use getAvailableServerPort()?

[PeterSchafer]

Question: Is there any explanation why this change has an effect on flakiness?

[PeterSchafer]

In general it is the right move to use this pattern but for other reasons then flakiness in my understanding.

[danskmt]

it seems he's applying the pattern in other tests, so sounds correct.
For the flakiness, it might be the timeout increase to fix it:

[robertolopezlopez]

I was writing a comment here, it turned to be the same as this

For the flakiness, it might be the timeout increase to fix it

[PeterSchafer]

yes, I added the timeout ;)

[snyk-pr-review-bot]

PR Reviewer Guide 🔍

🧪 PR contains tests

🔒 No security concerns identified

⚡ No major issues detected

📚 Repository Context Analyzed This review considered 3 relevant code sections from 3 files (average relevance: 1.00) CONTRIBUTING.md (lines 1-231) package.json (lines 1-229) help/cli-commands/test.md (lines 241-421)

🤖 Repository instructions applied (from AGENTS.md)