feat: support clearLockedPorts

[nanianlisao]

Previously, lockedPorts was not exported, which made it impossible to clear the cache.

By exporting lockedPorts, we can now manipulate it directly, allowing for cache clearing when necessary. This change will improve the flexibility of the library and allow users to better control the state of their applications.

Here is a brief overview of the changes:

• Added an export for lockedPorts in the main library file.
• Updated the documentation to reflect this new feature.

Please review these changes and let me know if you have any questions or concerns. Thank you for considering this contribution.

[sindresorhus]

I don't think this should be exported. If the need is to clear the cache, a clear cache function should be exported.

This contribution also feels ChatGPT generated. If it is, it should be made clear that it is.

[nanianlisao]

@sindresorhus
Thank you for your feedback.
Indeed, I only need to clear the internal cache to ensure that each time getPort is called, the result is not interfered with.

I've changed it to export a function.

[nanianlisao]

thx

[sindresorhus]

The docs should also note that clearing the cache could cause race conditions, since it makes this no longer true:

Race conditions in the same process are mitigated against by using a lightweight locking mechanism where a port will be held for a minimum of 15 seconds and a maximum of 30 seconds before being released again.