fix(search): give engines room to finish, and add ones a datacenter IP is allowed

Two separate problems shared one symptom, so they were being read as one.

SearXNG's outgoing.request_timeout was 5.0. DuckDuckGo from a datacenter IP
routinely takes 5-7s, so SearXNG gave up on it and listed it unresponsive — the
identical "engine is broken" report a block produces, for an engine that was
only slow. Raised to 9.0, with Ael's race budget raised to match, so an engine
is judged on the results it returns rather than on our impatience. The happy
path is unaffected: the race still finishes on the first viable set.

Google and Wikipedia answer 200-with-nothing from Hugging Face's shared egress
IP. That left Bing carrying every query with no redundancy, which is not
resilience — a single-IP block on the one working engine takes out search
entirely. Added mojeek, marginalia, rightdao, mwmbl, presearch and qwant: the
engines that still answer a datacenter IP without a CAPTCHA, and deliberately
redundant with each other.

The pre-existing google/duckduckgo/bing/wikipedia entries are kept. A rate limit
is not a ban, and an engine that recovers should be picked up without another
config edit.

searxng_settings.yml

@@ -24,8 +24,14 @@ ui:
   static_use_hash: true
 
 outgoing:
-  request_timeout: 5.0
-  max_request_timeout: 15.0
+  # 5.0 was killing engines that legitimately need longer. DuckDuckGo from a
+  # datacenter IP regularly takes 5-7s, so at 5.0 SearXNG abandoned it and
+  # reported it unresponsive — the same "engine is broken" symptom a block
+  # produces, for an engine that was merely slow. Ael's race budget is 12s, so
+  # there is headroom to let the engine finish and be judged on its results
+  # rather than on our patience.
+  request_timeout: 9.0
+  max_request_timeout: 20.0
   useragent_suffix: ""
   pool_connections: 100
   pool_maxsize: 20
@@ -65,3 +71,38 @@ engines:
     engine: arxiv
     shortcut: ar
     disabled: false
+
+  # Added 2026-09-30. Google and Wikipedia both answer 200-with-nothing from
+  # Hugging Face's shared egress IP, which left Bing carrying every query. These
+  # are the engines that still answer a datacenter IP without a CAPTCHA, and
+  # they are redundant with each other on purpose: the failure being fixed is
+  # a single-IP block, and one working engine is not resilience.
+  - name: mojeek
+    engine: mojeek
+    shortcut: mjk
+    disabled: false
+
+  - name: marginalia
+    engine: marginalia
+    shortcut: mg
+    disabled: false
+
+  - name: rightdao
+    engine: rightdao
+    shortcut: rdao
+    disabled: false
+
+  - name: mwmbl
+    engine: mwmbl
+    shortcut: mw
+    disabled: false
+
+  - name: presearch
+    engine: presearch
+    shortcut: ps
+    disabled: false
+
+  - name: qwant
+    engine: qwant
+    shortcut: qw
+    disabled: false