fix(seeder): force HTTP/1.1 ALPN in proxy tunnel to prevent h2 parse error (koala73#2454)

* chore: redeploy to pick up WORLDMONITOR_VALID_KEYS fix

* fix(seeder): force HTTP/1.1 ALPN in proxy tunnel to prevent h2 parse error

api.stlouisfed.org supports HTTP/2. tls.connect() includes h2 in ALPN by
default, causing the server to negotiate HTTP/2. But https.request uses
HTTP/1.1 parser, so HTTP/2 binary frames fail with:
  Parse Error: Expected HTTP/, RTSP/ or ICE/

Fix: ALPNProtocols: ['http/1.1'] forces HTTP/1.1 over the tunnel.

* fix(seeder): increase FRED direct fetch timeout 10s→20s

WALCL is first in FRED_SERIES and fires at cold container start.
TCP + TLS + FRED API response on a cold connection was hitting the 10s
limit. All other series benefit from the established connection pool.
20s matches the original curl --max-time 15 plus handshake overhead.

Author: koala73

scripts/_seed-utils.mjs

@@ -369,7 +369,7 @@ async function httpsProxyFetchJson(url, proxyAuth) {
     }).on('error', reject).end();
   });
 
-  const tlsSock = tls.connect({ socket, servername: targetUrl.hostname });
+  const tlsSock = tls.connect({ socket, servername: targetUrl.hostname, ALPNProtocols: ['http/1.1'] });
   await new Promise((resolve, reject) => {
     tlsSock.on('secureConnect', resolve);
     tlsSock.on('error', reject);
@@ -408,7 +408,7 @@ async function httpsProxyFetchJson(url, proxyAuth) {
 // Fetch JSON from a FRED URL, routing through proxy when available.
 export async function fredFetchJson(url, proxyAuth) {
   try {
-    const r = await fetch(url, { headers: { Accept: 'application/json' }, signal: AbortSignal.timeout(10_000) });
+    const r = await fetch(url, { headers: { Accept: 'application/json' }, signal: AbortSignal.timeout(20_000) });
     if (r.ok) return r.json();
     throw Object.assign(new Error(`HTTP ${r.status}`), { status: r.status });
   } catch (directErr) {