devproxy logs silently picks one instance when multiple are running #1932

Description

When several Dev Proxy instances are running, stop and status without --pid act on all of them. devproxy logs without --pid instead quietly picks one: the system-proxy instance first, otherwise the most recently started. It doesn't say which instance it chose or that other instances exist.

Evidence

• DevProxy/Commands/LogsCommand.cs:65 calls StateManager.LoadStateAsync
• DevProxy/State/StateManager.cs:110-117 orders by AsSystemProxy, then StartedAt, and takes FirstOrDefault()
• stop and status iterate over LoadAllStatesAsync

Expected

Either behave like stop/status when multiple instances are running (for example, list the instances and ask for --pid), or at least print which instance (PID) the logs come from and point to --pid for the others.