Run multiple ewc on the next port

We have long running tasks and with the current setup it starts a server on `:22322` but fails to start if one already exists. This should be handled like vite where `:5173` is the default and if one exists there it automatically launches on `:5174`.

The goal is to not be forced to close the long running ewc session in order to fix a small issue or demonstrate something

Start by locating the ewc server startup and default :22322 port handling, then compare its behavior with the Vite-style fallback described in the issue. Done means a second running ewc instance automatically selects the next available port instead of failing.

Written by the indexing model from the issue text.