Hook in APIs to filtered permissions data component

[JackHaeg]

Dependency

• [ ] This issue is not to be assigned/worked on until #1754 has been completed, and API issues (#1770 & #1771) PRs have been approved.

Overview

This issue represents the final step in the User Permission Search Epic. The objective is to remove the placeholder dummy data currently used in the "User Permission Search" screen and integrate the APIs developed earlier in the Epic. Once completed, the filtered permissions data component will be fully functional and ready for production.

Action Items

• Remove Dummy Data
  • [ ] Identify and remove all instances of dummy/placeholder data from the "User Permission Search" screen and filtered permissions data component.
• API Integration
  • [ ] Hook up the previously created APIs to the filtered permissions data component:
  • For Admin: https://github.com/hackforla/VRMS/pull/1774
  • For Project Leads: https://github.com/hackforla/VRMS/pull/1799
  • [ ] Ensure the API responses are correctly mapped to the UI elements and behave as expected.
• Testing
  • [ ] Verify the full flow from user input to permission search results.
  • [ ] Ensure that the search results update dynamically based on input filters.
  • [ ] Conduct both unit tests and end-to-end tests to validate the functionality and catch any edge cases.

Resources/Instructions

Screenshot of User Permission Search Screen mockups

• Low-fi mockups created by Bonnie / Jack - see page 2 of mockups
• This issue is part of this epic: #1737

[JackHaeg]

@trillium Please add an action item to address any remaining dummy data objects, values, or properties not currently included in our code, as noted by Vorleak in this PR https://github.com/hackforla/VRMS/pull/1808#issuecomment-2453863654