feat(api-v2): Return events describing version history of resources and values of a project ordered by data (DSP-1528)

[SepidehAlassi]

resolves DSP-1528

[benjamingeer]

How is the performance if you get the full history of a project with a lot of data?

[SepidehAlassi]

How is the performance if you get the full history of a project with a lot of data?
For anything project that has only 52 resources, it returns 88 events in 50 seconds. Probably if a project had thousands of resources, it will take pretty long and crash as soon as the time threshold is reached. The task in DSP-1528 was to write a route that gets project IRIs and returns the entire history of resources as events, and this PR does that. The performance issue would be something that definitely will come up.

I have already thought about this issue though. I have already written the responder, getResourceHistoryEvents, that gets the IRI of a resource and returns history events for it. I could change it a bit and add a route for it, i.e. GET request that returns the events for a given resource IRI. There is also this template to get all resources of a project. I could also add a route, a GET request that returns a list of resource IRIs for a given project IRI. Then the DSP tools could first use the latter route to get the resource IRIs and then could iterate over them and call the first route to get the events of that each resource and store them somewhere.

[benjamingeer]

This looks good now, thanks very much!