Gate network parsers on a working proxy and remember what worked

The pool now warms up from what the previous run learned instead of starting
cold every launch. Startup probes the remembered proxies first, stops as soon
as ProxyMinimumLive of them answer, and writes the survivors to
proxies.state.json after the warm-up and again on shutdown. Only proxies that
ever answered are stored: the feed republishes a few thousand dead addresses
every five minutes, and "was dead an hour ago" says almost nothing.

Remembered state is a hint, not a verdict. A restored proxy sorts first in the
warm-up queue but is not counted live until it answers in this session -
otherwise a launch a week later would report live proxies it had never spoken
to, the warm-up would skip the very entries it exists to re-check, and the
parser gate would open on week-old evidence.

That gate is the other half: a parser declaring RequiresNetwork will not run
while the pool has nothing live. The Parse page disables the run button and
shows a banner that leads to the Proxies page. Parsers that work on pasted text
are never gated - they have nothing to route, and blocking them would make the
app useless whenever the public lists are down. Two new settings cover the
escape hatch and the target: "allow network parsers without a proxy" and how
many live proxies to find at startup.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

src/AvParser.UI/DependencyInjection/UiServiceCollectionExtensions.cs

@@ -34,6 +34,8 @@ public static class UiServiceCollectionExtensions
         services.AddSingleton<ParseViewModel>(static sp => new ParseViewModel(
             sp.GetRequiredService<IParserCatalog>(),
             sp.GetRequiredService<ISettingsService>(),
+            sp.GetRequiredService<IProxyPool>(),
+            sp,
             sp.GetRequiredService<ILogger<ParseViewModel>>()
         ));
         services.AddSingleton<SettingsViewModel>(static sp => new SettingsViewModel(