As part of estimating the impact of Parallel CQ on our test fleet capacity, we need to know which ebuilds are required for each build target. This will aid in historical commit analysis, so we can map changes to particular source roots in the repos to the set of builders that would be affected by those changes.

We can grab the data for a such a map from recent builds, using the generated build-events.json files from each Paladin run.