aggregate_content_datasets: Use revision-in-origin table of the provenance

Currently, aggregate_content_datasets looks for a revision that contains each content object, and an origin that contains that revision. Looking up origins from revision takes days for the last handful of revisions. Instead, aggregate_content_datasets should use the provenance database, which already has this information (and is computed more efficiently)