fix(serve): improve error message when port is in use

[beeman]

No description provided.

[abdel-ships-it]

We can do better than this, time to automatically detect new ports!

[beeman]

This has been suggested but the team decided against it. They don't want to automatically run on a random port when it's in use.

If the developer likes to do this there is the option --port 0

[abdel-ships-it]

@beeman We should better inform the developers about the existence of that specific flag value. Is it maybe an idea to addd that to the error message?

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}