Provide a collection resource where a version history can be obtained (`version-history`, `predecessor-version` and `successor-version` link relations)

#2992833: Add a version negotiation to revisionable resource types → makes it possible to request individual revisions of an entity.

In order to find those revisions, a version-history resource is required which will list all revisions of an entity.

We need to:

1. Determine what the URL path should be.
2. Figure out how individual resource objects in the collection will link directly to their revision-specific individual route. See #2992836: Provide links to resource versions (entity revisions) →
3. Implement it!