[BLOCKED] [CCP] (#2) Modify vets-api to handle pagination from CCP PPMS and verify that vets-website facility locator is resolving pagination correctly

[eselkin]

Status

2024-08-06] Blocked by #17646

User Story or Problem Statement

As a user, I want to see an increasing number of results on CCP searches in facility locator when it is zoomed out on an area with more data. That data should be in a paginated format like lighthouse results.

Description or Additional Context

Steps for Implementation

1. Modify vets-api pagination to capture page (page, per_page, and total entries) information
2. Add tests to spec to guarantee pagination works for CCP vets-api endpoint
3. Verify that vets-website facility locator can page through results from CCP endpoint (it should use the same abstraction for pagination/wrapper as VA endpoints)
4. Add tests in vets-website to check that facility locator can page through CCP endpoint results.

Acceptance Criteria

• vets-api should return data with next_page attributes when more than 10 entries
• vets-api should be able to return subsequent results of CCP search when queries with page > 1
• vets-website should show multiple pages when total entries greater than 10
• Requires design review
• Requires accessibility review

[jilladams]

Spike notes: #17418 (comment)

[jilladams]

Calling this blocked until our team gets GFE in order to work on PPMS in vets-api.

[jilladams]

Noting: I just observed a flipper in prod, facility_locator_restore_community_care_pagination - we should think about this once we take up the pagination effort, and figure out if it's in use / can be deprecated. Related ticket: #11597

[davidmpickett]

@eselkin Is this still blocked, or could it move now?