Fix issues about reusing data when triggering updates
When triggering updates from the dashboard, the pipeline is meant to use the same package data that generated the dashboard for consistency. This makes it more consistent (the packages that get updated are the one reported on the dashboard) and faster (no need to re-scan the world).
This MR fixes a couple of issues with that and move to use data.yaml to be able to use the full data later on.
