Raise default Chorus local-op timeout so large projects can S/R

Chorus's 15-minute default timeout on local hg operations (e.g. the
post-merge commit) is too short for very large projects, which then land
on hold with a TimeoutException (#357). Default CHORUS_LOCAL_TIMEOUT_SECONDS
to 3600 in environ, and pass it through both lfmergeqm launch scripts'
sudo --preserve-env so a deployment can still override it.

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

Author: myieye

environ

@@ -9,3 +9,9 @@ export PATH="${BASE}/output/${BUILD}/net8.0:${BASE}/output/Mercurial:${PATH}"
 # set HGRCPATH so that we ignore ~/.hgrc files which might have content that is
 # incompatible with our version of Mercurial
 export HGRCPATH=/etc/mercurial/hgrc
+
+# Chorus's 15-min default timeout on local hg ops is too short for very large
+# projects, whose merge commits can exceed it and land the project on hold
+# (https://github.com/sillsdev/LfMerge/issues/357). Overridable per deployment via
+# CHORUS_LOCAL_TIMEOUT_SECONDS, passed through by the launch scripts' --preserve-env.
+export CHORUS_LOCAL_TIMEOUT_SECONDS=${CHORUS_LOCAL_TIMEOUT_SECONDS:-3600}

lfmergeqm-background.sh

@@ -5,6 +5,6 @@
 
 while :
 do
-  sudo -H --preserve-env=CHORUS_HG_EXE -u www-data lfmergeqm
+  sudo -H --preserve-env=CHORUS_HG_EXE,CHORUS_LOCAL_TIMEOUT_SECONDS -u www-data lfmergeqm
   sleep 86400
 done

lfmergeqm-looping.sh

@@ -10,7 +10,7 @@ trap "exit" TERM
 # This is expected to run as the CMD, launched by the entry point.
 
 while inotifywait -e close_write /var/lib/languageforge/lexicon/sendreceive/syncqueue; do
-  sudo -H --preserve-env=CHORUS_HG_EXE -u www-data lfmergeqm
+  sudo -H --preserve-env=CHORUS_HG_EXE,CHORUS_LOCAL_TIMEOUT_SECONDS -u www-data lfmergeqm
   # Run it again just to ensure that any initial clones that missed a race condition have a chance to get noticed
-  sudo -H --preserve-env=CHORUS_HG_EXE -u www-data lfmergeqm
+  sudo -H --preserve-env=CHORUS_HG_EXE,CHORUS_LOCAL_TIMEOUT_SECONDS -u www-data lfmergeqm
 done