Studio: Refactor windows port checker to use portFinder helpers

[gavande1]

Related issues

• Fixes STU-103

Note

We also have checkPortInWindows in src/lib/proxy-server.ts. There's an obvious difference in that the checkPortInWindows function only runs on Windows, but I still wonder if we shouldn't refactor that function and PortFinder::isPortFree to share the same underlying logic.

• Studio: Check if port is open before starting servers #1236 (comment)

Proposed Changes

• Refactor Windows port checker to use portFinder helpers

Testing Instructions

1. Check out the branch on a Windows machine.
2. Open a new terminal tab and run:

   php -S localhost:80

3. In another terminal tab, start Studio by running:

   npm start

4. Confirm that you receive an alert indicating the port is busy (similar to the screenshots provided).

5. Stop Studio (Ctrl+C in the terminal).
6. Cancel the PHP server process (Ctrl+C in the other terminal).
7. Wait a few seconds to ensure both processes have fully stopped.
8. Start Studio again by running:

   npm start

9. Confirm that this time, you do not receive any alert about the port being busy.

Pre-merge Checklist

• Have you checked for TypeScript, React or other console errors?

[fredrikekelund]

Elegant and works as expected 👍

Not directly related to this PR, but I noticed this error message:

Studio needs to use port 80 and 443 to enable custom domains and SSL, but one of both of these ports are already in use by another app. Close any local development apps and restart Studio.

I would remove "of both" from that message to make it sound more idiomatic. I.e., it would read:

Studio needs to use port 80 and 443 to enable custom domains and SSL, but one of these ports are already in use by another app. Close any local development apps and restart Studio.

[bcotrim]

LGTM 👍

[fredrikekelund]

LGTM with two nits 👍