Return the history of actions on a given resource

[imsdu]

Motivation
For a client, it is currently not possible to have an clear idea of the different actions applied to a resource during its lifetime.

Acceptance criteria

1. The user must have access to the resource
2. The events are returned in chronological order
3. No pagination is applied
4. For each event, we return the action, the timestamp of the event and the author

Implementation notes
This endpoint must rely on the events metric index so an Elasticsearch query must be written.
The implementation must be in the Elasticsearch plugin as this is where the ES dependency is at the moment
The api endpoint can be:
/resources/org/project/_/[resource_id]/history
(_ being the schema and is not relevant here)
And would be implemented in ElasticSearchQueryRoutes along the listing operation

[ssssarah]

• Would each event be tied to a revision number?
• I wonder how much visibility/action we would have on querying based on time. ex: from/to filters with date input or rev input.

I'm thinking of the following use case:
Knowing the differences between the same resource between a version at time x and the version at time y.

The process would be to

• 1. Identify with this endpoint the revisions to target
• 2. Compute the diff with Add an endpoint to compare two resources #4787

Another option would be to extend the proposal of #4787 to add comparison based on time?

[imsdu]

• Every event is tied to a revision number internally
• It can be a good idea. However this is only the Delta endpoint in this ticket, I preferred to keep it simple waiting for the Fusion ticket. Depending on this second ticket, we will see if we want filters which would be applied on the frontend side or something to include in the endpoint.