build(llard): install autotools dependencies

[MeteorsLiu]

Equip the llard runtime image with the GNU source bootstrap tools required by Formula builds.

The implementation includes:

• Install autoconf, automake, and gperf for projects that generate Autotools build files from Git source checkouts.
• Install groff for upstream documentation generation and patch for gnulib bootstrap steps.
• Keep the tools in the final Debian image alongside the existing compiler, CMake, Git, and pkg-config toolchain while retaining --no-install-recommends and apt-list cleanup.

This allows llard workers on both published Linux architectures to build packages whose repositories omit generated configure files.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[fennoai]

Review: add autotools build tools to llard image

The change adds autoconf, automake, gperf, groff, and patch to the runtime image's apt install list. This is consistent with the purpose of llard: it's the build daemon that shells out to build tools (via execbroker) to compile C/C++ libraries from source formulas at runtime, so autotools-based formulas (autoreconf, patch application, perfect-hash generation) need these present. Placement is correct, alphabetical ordering is preserved, and the existing hygiene (--no-install-recommends, cleanup of apt lists, non-root user) is kept.

Two minor, non-blocking notes below. No blocking issues.

Note: several review heuristics flagged "build tooling in a runtime image" as an attack-surface concern. That premise doesn't hold here — executing build tools at runtime is the daemon's core function, not an anti-pattern — so it's intentionally not raised as a finding.

[fennoai]

[P3] Consider groff-base instead of full groff

groff pulls in a fairly large typesetting/documentation stack. If it's only needed so source builds can regenerate man pages (e.g. via help2man/makeinfo), groff-base is a smaller drop-in that covers most such needs. Worth confirming which a concrete formula actually requires; keep full groff if something genuinely depends on it.

[fennoai]

[P3] Unpinned package versions affect build reproducibility

None of the apt packages are version-pinned (pre-existing pattern; these additions just follow it). Rebuilds are therefore non-reproducible and a toolchain upgrade could silently change how formulas build. Not a blocker for this PR — noting as a possible repo-wide follow-up (pin versions or document reliance on the bookworm snapshot).