Remember randomly selected ports, and don't reuse them

[shauns]

WHY are these changes introduced?

To prevent port conflicts when multiple processes request random TCP ports in quick succession. If a caller doesn't use a port immediately, a duplicate random port can be chosen.

WHAT is this pull request doing?

Enhances the getAvailableTCPPort function to track previously obtained random ports and ensure they aren't reused within the same process. This is accomplished by:

1. Adding a obtainedRandomPorts Set to keep track of ports that have been assigned
2. Adding logic to check if a random port has already been obtained and retry if necessary
3. Adding the obtained port to the tracking Set before returning it

Added a test case to verify that random ports are not reused.

[shauns]

• Specific methods for patch app configuration file scenarios #5641 : 2 dependent PRs (#5642 , #5677 )
• Remember randomly selected ports, and don't reuse them #5685 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

We detected some changes at packages/*/src and there are no updates in the .changeset.
If the changes are user-facing, run "pnpm changeset add" to track your changes and include them in the next release CHANGELOG.

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	76.72% (+0.02% 🔼)	9513/12399
🟡	Branches	71.85% (+0.03% 🔼)	4678/6511
🟡	Functions	76.47% (+0.01% 🔼)	2464/3222
🟡	Lines	77.25% (+0.02% 🔼)	8993/11641

Test suite run success

2218 tests passing in 966 suites.

Report generated by 🧪jest coverage report action from 539c002