vinca-gha: stage the generated recipes without resolving the distribution again

[Tobias-Fischer]

vinca-gha called get_full_tree(), which regenerates the outputs of every package of the distribution (build_all, ~1900 packages for lyrical: package.xml downloads, SPDX license normalisation, mutex generation again), only to read their host/run dependency names. vinca (generate-recipes) has just written the recipes the workflow orders, so their own requirements.host/run are enough to build the graph. vinca.yaml is still read (cheaply) for ros_distro and the pixi versions.

Side effects:

• Recipes the build_all tree lacked are no longer dropped. build_all uses the live rosdistro release packages, so a recipe for a snapshot package that is no longer in the index was silently left out of the workflow ("filter out packages that we are not actually building"). In lyrical that hit easynav_gps_localizer, roboplan_common, roboplan_core (and dependents of the latter were staged without waiting for them).
• Dependencies through packages that are not rebuilt (already on the channel) no longer order the stages: if A -> B (published) -> C (rebuilt), A and C can now share a stage. A only needs the C build that B was built against, so this ordering wasn't needed; if B has to pick up the new C it is rebuilt too and then in the recipes.
• Recipe files are read in sorted order, so the job order doesn't depend on the file system.

Measured locally (RoboStack monorepo, rs <distro> generate-recipes then rs <distro> gha --batch-size 25, vinca = current robostack-integration with/without this commit):

distro / platform	recipes	before	after
lyrical linux-64	167	61.4 s	2.7 s
lyrical osx-arm64	109	60.2 s	2.3 s
jazzy linux-64	73	55.1 s	2.4 s
humble linux-64	31	179.5 s	1.8 s
lyrical linux-64, no skip_existing	2235	36.2 s	7.3 s

The workflow is not byte-identical: within a dependency stage the package order (and so which packages share a batch job) followed the topological order of the full tree and now follows the recipes. Every package's dependency stage is identical: same jobs and per-package stage for jazzy/humble linux-64 and lyrical osx-arm64; for lyrical linux-64 the only differences are the packages listed above that were previously dropped, and the roboplan packages that now wait for roboplan_core. The host/run dependency names read from the recipes equal those of the full tree for all 2229 common packages.

Tests: get_recipe_requirements and a main() test that stages recipes from ./recipes without resolving anything; full vinca suite passes (263 passed).

🤖 Generated with Claude Code

[traversaro]

GReat! After you fix the conflict, I guess this is ready to merge.