Share tunnels on the HTTPS port, and show them as a status badge

[splitbrain-bot]

Two follow-ups from testing #85 on the deployment.

Tunnel URLs on port 443

The service now lists two URLs per tunnel port, in this order:

https://7twd9fqf.euw.devtunnels.ms:3000/
https://7twd9fqf-3000.euw.devtunnels.ms/

The skill and the orchestrator both took the first one, so a shared app needed port 3000 (or whatever the app's port is) open on the visitor's network. Both now take the URL on the standard HTTPS port:

• orchestrator/src/tunnels.ts picks the URL without a port of its own. A remembered row with a :port URL is shown in the -port form too, so existing rows need no cleanup.
• The skill's URL step uses a jq filter that picks the same form.

A status badge instead of the globe link

The globe marker next to the disk use read like a measurement. The card now shows a shared status badge (or "2 shared") right after "still running", with a purple dot (--shared: #a78bfa, a new status colour). The info page shows it in its badge row too, and still lists the URLs.

Testing

• Orchestrator: the URL choice on a service-shaped answer, and the fallback for a remembered :port URL.
• Dashboard: the card test checks the badge.
• On the deployment (before this change): the automatic cleanup deleted a tunnel 7 minutes after its host process stopped, as designed (5 min grace plus up to two minute ticks).