test: improve port handling stability in api.test.js

[negimox]

• This is a bugfix
• This is a feature
• This is a code refactor
• This is a test update
• This is a docs update
• This is a metadata update

For Bugs and Features; did you add new tests?

Motivation / Use-Case

The test file api.test.js is unstable when "PORT" access isn't available, which results in the test suite failing.

Breaking Changes

Additional Info

[negimox]

Hello @alexander-akait, can you review this PR? I'm not sure if this is the correct way to resolve the unstable test cases, can you tell me your thoughts about it?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.36%. Comparing base (af6bd68) to head (118dd3a).
Report is 115 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #5433      +/-   ##
==========================================
- Coverage   90.29%   83.36%   -6.94%     
==========================================
  Files          15       13       -2     
  Lines        1577     2026     +449     
  Branches      601      742     +141     
==========================================
+ Hits         1424     1689     +265     
- Misses        140      303     +163     
- Partials       13       34      +21     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[alexander-akait]

Why we need this?

[negimox]

I added that because,

• Without this handling, tests sometimes fail unpredictably with "permission denied" errors which occurs due to Windows environments often having stricter port access permissions.
• These failures block CI pipelines despite the actual code being correct.

[alexander-akait]

I am afraid it can create flaky tests, i.e. we will have green CI, but tests are failed, let's rewrite it - try to test 3 times, if failed our CI should failed

[negimox]

And @alexander-akait, one request whenever you are free can you please take a look at my proposal for GSOC 2025? Any pointers on what I could change, improve or modify will be very helpful for me.
https://www.notion.so/DRAFT-Unified-Webpack-Dev-Tools-GSoC-2025-Project-Proposal-1b6d2d371bfa8030ba41e9907c101927?pvs=4

[alexander-akait]

@negimox Unfortunately, I don't work with proposals, other developers from our TCS (you can find them on webpack readme page) are doing this

[negimox]

@negimox Unfortunately, I don't work with proposals, other developers from our TCS (you can find them on webpack readme page) are doing this

Hello @alexander-akait , I'll take a look at the webpack readme page and reach out to the appropriate team members. If you have any tips on who to contact first, that would be really helpful! But thank you for responding.

[negimox]

@alexander-akait I have changed its functionality to retry 3 times. Could you verify if this implementation correct for retry?

[alexander-akait]

Can you fix it for all tests? Because we have the same logic for other tests

[negimox]

Can you fix it for all tests? Because we have the same logic for other tests

Yes, I can do that. Should I start a new PR for that?

[alexander-akait]

@negimox I mean fix it for all test in this file