This adds a paginated listing endpoint so authenticated user can retrieve their deposit
information in batch. This touches another part of an equivalent private listing api [1]
to allow paginated code reuse.
It's not a sword endpoint but it lists deposits in xml nonetheless [2]
Next step if this lands as-is would be to open the use of such api to the deposit cli.
Discuss [2] ;)
[1] The "all" listing api used in the admin deposit view of the webapp
[2] Checking the spec for the listing collection endpoint [3) kinda took me aback...
Thus why i removed the easy-hack from the task (i had also forgotten it was one...). In
there it says, well do an atompub (and then forwards to the atompub rfc [4] and i got
lost in there... I kinda did not want to fall in there so i took another simpler way.
Also it's somewhat for internal use within the cli, so the exposal in the main server
is an implementation detail. Anyway, feel free to propose something better ;)
[3] http://swordapp.github.io/SWORDv2-Profile/SWORDProfile.html#protocoloperations_listingcollections
[4] https://www.ietf.org/rfc/rfc5023.txt
Related to T2996