Fix test failure: upgrade honcho to 2.0.0 for setuptools 82.0.0 compatibility

[Copilot]

Container startup was failing with ModuleNotFoundError: No module named 'pkg_resources'. honcho 1.1.0 depends on pkg_resources, which was removed from setuptools 82.0.0+.

Changes:

• Upgrade honcho from 1.1.0 to 2.0.0 (no longer uses pkg_resources)
• Add setuptools to requirements.txt (not included by default in Python 3.12+)

The fix ensures compatibility with modern Python and setuptools versions while maintaining the existing process management functionality.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• metadata.google.internal
  • Triggering command: /app/venv/bin/python python ./manage.py migrate (dns block)
  • Triggering command: /app/venv/bin/python python ./manage.py migrate apt-config shel�� ARCHIVE_KEYRING runtime-runc/moby /usr/bin/dpkg-deb io.containerd.ru/usr/bin/apt-key (dns block)
  • Triggering command: /app/venv/bin/python python ./manage.py migrate 36a/init.pid star�� yts40qpw3ok24rnvg9r3ut432 /usr/bin/git /usr/sbin/dpkg-split 14d6d8a46c821957gpgv p.ci ctl dpkg-split -Qao�� /var/lib/dpkg/re--ignore-time-conflict /tmp/apt-dpkg-in--status-fd ine (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[fr4nc1sc0-r4m0n]

LGTM