Tech debt: Use Link headers to paginate rather than manual pagination

Current Project API pagination is brittle due to the current manual method of pagination within the ProjectsService. This was done as an acceptable stopgap to go live, and a better fix that makes use of Link Headers should be used.

On the initial investigation, there was no found way to easily extend the RESTeasy API builder model. If this model can be extended, then adding a post-process to the responses to attach Link headers to the response output can be used to more sustainably iterate over the data. If there is no way to extend this model, then a concrete implementation will need to be created for the Projects REST API over the generated implementation.

changed title from Tech debt: Use Link headers to paginate rather than manual pagination to Tech debt: Use Link headers to paginate rather than manual pagination

changed the description

added 1 deleted label

added Enhancement label

changed milestone to %1.0

added statetodo label

added to epic eclipsefdn&15 (closed)

assigned to @malowe

assigned to @zacharysabourin and unassigned @malowe

There is a service called APIMiddleware that does pagination using the headers referenced above, so we should be able to use that. An example of how this is used with cache can be seen https://gitlab.eclipse.org/eclipsefdn/it/websites/membership.eclipse.org/-/blob/master/portal/src/main/java/org/eclipsefoundation/membership/portal/service/impl/DefaultProjectsService.java#L100

added statewip label and removed statetodo label

mentioned in commit zacharysabourin/git-eca-rest-api@e18245ab

mentioned in merge request !97 (merged)

added statedone label and removed statewip label

closed

removed statedone label