The first-open real-profile consent dialog gated only on config/opt-out
state, so over a remote (SSH/URL/cloud) connection it offered "your
default browser's profile" and "Enable" wrote browser.use_real_profile
into the REMOTE config.yaml, where that machine's browser (often none)
is used. It then re-offered itself after every reset of the flag.
Gate the prompt on the live resolved connection being local via a pure
shouldOfferRealProfilePrompt(); an unresolved connection fails closed.
Remote users can still opt in from Capabilities -> Tools -> Browser.
Fixes#119398
a266cf5e60