List and populate contents per revision in cache_content_revision (api endpoint)

We need to populate the cache_content_revision table of the content provenance information database.

For this, we need to be able to list for a given revision, the targeted tree and retrieves all {revision, content, path} data.

And copy those data in cache_content_revision.