fix(cli)!: Remove default port for --live-reload

[OS-pedrogustavobilro]

Description

This PR removes the default --port value for --live-reload. When adding the --https, we already opted out of having a default, and with this (breaking) change there's consistency.

With this PR, if no --port nor --http is specified, the url will be like so http://<host>; in other words, will run in the default port for http (80).

An alternative to this is to merge --host, --port, and --https CLI args into a single --url or --live-reload-url arg, that would directly override server.url config. I am inclined to open a separate PR for that and the team can decide which one is preferable.

Change Type

• Fix
• Feature
• Refactor
• Breaking Change
• Documentation

Rationale / Problems Fixed

Port '3000' isn't widely used for local servers, maybe it made sense once upon a time, but not anymore.

There has been confusion regarding the use of a default port for --live-reload (there's probably older links, but these should suffice to justify the change):

• [Bug]: cap run ignores server config #8303
• feat(cli): Add --https option for --live-reload #8194 (review)

Since the port may change depending on what's the underlying stack used to setup live-reload, the framework shouldn't make assumptions on the port to use.

Tests or Reproductions

You can use any existing capacitor app to test, you just need to point to the local capacitor cli version from this PR's branch.

For reference, I used https://github.com/OS-pedrogustavobilro/capacitor-test-livereload

Screenshots / Media

Not relevant

Platforms Affected

• Android
• iOS
• Web

Notes / Comments

N/A

[jcesarmobile]

I personally prefer a single --url param rather than having to pass 4 different params: --live-reload, --host --port and --https, with undocumented defaults if you don't pass some of them.

When you run a dev server and/or ngrok they usually tell you, the app is running on http://192.168.1.53:3713/https://4f8a-83-53-7-217.ngrok-free.app or similar message, so with --url you could simply copy the whole url and paste as the --url param, while with current implementation you have to pass --live-reload --host 192.168.1.53 --port 3713, or if using ngrok not pass the --port, but pass --https.

Also I find --live-reload param very confusing, we just changed the description recently to try to make it cleared, but still the param name is confusing as it doesn't really allow live reload, it just configures the server.url, whether it points to a server that supports live reload or not, and doesn't do any "live reload magic" by itself.