test(gate): fix the last 4 readiness/config false-fails (none are product bugs)

On a proper on-node .228 run (synced bitcoin, 4-fix binary) the lifecycle matrix is
green; these 4 were test-harness issues:
- lnd 'recovers after restart' (65): bump retry window 90s->240s. lnd cold-restart
  recovery (wallet unlock + bitcoind reconnect + graph sync) exceeds 90s on a loaded
  node but DOES complete (synced_to_chain:true).
- bitcoin ui responds (89): retry ~120s instead of single-shot (companion nginx may
  have just been recreated by the companion-survives test).
- probe_app_url (99 lnd proxy + all ui-coverage proxy probes): retry up to 90s for
  post-restart proxy/UI readiness instead of single-shot.
- required endpoints after restart (94): :8081 is nginx-proxy-manager, an OPTIONAL
  app (not in required_containers) — only assert it when NPM is installed; and make
  the trailing lncli getinfo a retry.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

tests/lifecycle/bats/lnd.bats

@@ -110,8 +110,10 @@ teardown_file() {
   [[ "${ARCHY_ALLOW_DESTRUCTIVE:-0}" == "1" ]] || skip "ARCHY_ALLOW_DESTRUCTIVE not set"
 
   # lnd takes longer than bitcoind to accept RPC after cold restart because
-  # the wallet has to be unlocked first. Give it 90s.
-  local deadline=$(( $(date +%s) + 90 ))
+  # the wallet has to be unlocked first, then it reconnects to bitcoind and
+  # re-syncs the graph. On a loaded node this exceeds 90s (observed ~2min on
+  # .228, then synced_to_chain:true). Give it 240s.
+  local deadline=$(( $(date +%s) + 240 ))
   while (( $(date +%s) < deadline )); do
     if sh -lc 'podman exec lnd lncli \
         --tlscertpath /root/.lnd/tls.cert \