Adding filtering and pagination to collectionList APIs

[stevenwinship]

What this PR does / why we need it: Result lists for collections can be quite large so a way to filter and use pagination is needed.

Which issue(s) this PR closes:#12423

• Closes Update collectionList API: add pagination and filtering #12423

Special notes for your reviewer: Switched to family "A" pagination. I did not change the output from "data.items" to "data" since that would be a breaking api change and data also contains count and totalCount.

Suggestions on how to test this: See DataRetrieverApi tests. create many dataverses owned or given access to a user. Test getting the list with and without pagination. Get the list as a superuser. Filter the list with a sort term.

Does this PR introduce a user interface change? If mockups are available, please link/include them here:

Is there a release notes update needed for this change?: included

Additional documentation:

https://dataverse-guide--12436.org.readthedocs.build/en/12436/api/native-api.html#list-dataverse-collections-a-user-can-act-on-based-on-their-permissions

[coveralls]

Coverage is 25.001% — 12423-collection-list-search-and-pagination into develop. No base build found for develop.

[github-actions]

Test Results

404 tests   389 ✅  25m 16s ⏱️
 55 suites   15 💤
 55 files      0 ❌

Results for commit e737ac1.

♻️ This comment has been updated with latest results.

[pdurbin]

At standup we talked about how we have various patterns for pagination, which I wrote about here: cfc5301

Family	Endpoint	Request parameters	Response keys
A	GET /api/datasets/{id}/versions/{versionId}/files	offset, limit	totalCount, data
A	GET /api/datasets/{id}/versions/compareSummary	offset, limit	totalCount, data
A	GET /api/notifications/all	offset, limit	totalCount, data
A	GET /api/files/{id}/versionDifferences	offset, limit	totalCount, data
B	GET /api/search	start, per_page	total_count, start, count_in_response, items
C	GET /api/admin/list-users	selectedPage, itemsPerPage	userCount, selectedPage, pagination{...}, users
C	GET /api/access/datafile/{id}/listRequests	start, per_page	data, pagination{...}
D	GET /api/users/{identifier}/allowedCollections/{permission}	offset, pageSize	count, items, pageSize, nextOffset, prevOffset
D	GET /api/mydata/retrieve/collectionList	offset, pageSize	count, items, pageSize, nextOffset, prevOffset

@stevenwinship will try to switch to the "A" family that the frontend expects.

Also, there's a Pager.java class at https://github.com/IQSS/dataverse/blob/v6.11/src/main/java/edu/harvard/iq/dataverse/mydata/Pager.java . We might want to create a new Pager class to rule them all. 💍

refactored

[sonarqubecloud]

Quality Gate failed

Failed conditions
9.5% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud

[github-actions]

📦 Pushed preview images as

ghcr.io/gdcc/dataverse:12423-collection-list-search-and-pagination

ghcr.io/gdcc/configbaker:12423-collection-list-search-and-pagination

🚢 See on GHCR. Use by referencing with full name as printed above, mind the registry name.