Show Proxy URL consistently in devproxy status output #2020

Description

The text output of devproxy status is inconsistent with detached startup output. Detached startup displays both Proxy URL and API URL, but status displays only API URL and a separate Port field for the forward proxy.

This makes it easy to mistake the management API URL for the forward proxy URL. During manual testing of #2009, this led to using the API port with curl --proxy and receiving HTTP 401 Unauthorized.

Steps to reproduce

1. Start Dev Proxy with OS-assigned ports:

   devproxy --detach --as-system-proxy false --port 0 --api-port 0

2. Observe that startup displays distinct Proxy URL and API URL fields.

3. Run devproxy status and compare the endpoint labels.

Actual behavior

Detached startup (unrelated fields omitted):

Proxy URL: http://127.0.0.1:37125
API URL:   http://127.0.0.1:46409

Status (unrelated fields omitted):

API URL: http://127.0.0.1:46409
Port:    37125

The status output contains the correct ports, but does not show a complete forward-proxy URL or clearly identify the port as belonging to the forward proxy.

Expected behavior

devproxy status should display both endpoint URLs with consistent labels, matching detached startup:

Proxy URL: http://127.0.0.1:37125
API URL:   http://127.0.0.1:46409

Environment

• Dev Proxy 3.3.1
• Debian/Ubuntu-based dev container on ARM64

This is an existing CLI UX inconsistency discovered while testing #2009, not a regression introduced by that PR.