[API-35332] View POA Requests - Filtering

[tycol7]

Summary

• add the filter key to the POA request with the following keys:
  • status, an array of enums (NEW, ACCEPTED, DECLINED)
  • state
  • city
  • country
• add tests and docs (v2 staging only)

Related issue(s)

API-35332

Testing done

• New code is covered by unit tests

Testing steps

1. Connect to BGS.

2. Send the following request:

   curl --location 'http://localhost:3000/services/claims/v2/veterans/power-of-attorney-requests' \
   --header 'Content-Type: application/json' \
   --header 'Authorization: Bearer *****' \
   --data '{
       "data": {
           "attributes": {
               "poaCodes": [
                   "002",
                   "003",
                   "083"
               ],
               "filter": {
                   "status": [
                       "ACCEPTED"
                   ],
                   "state": "TX",
                   "city": "Cedar Park",
                   "country": "USA"
               }
           }
       }
   }'
   

3. Observe the following response:

   [
       {
           "VSOUserEmail": "Beatrice.Stroud44@va.gov",
           "VSOUserFirstName": "BEATRICE",
           "VSOUserLastName": "STROUD",
           "changeAddressAuth": "N",
           "claimantCity": "CEDAR PARK",
           "claimantCountry": "USA",
           "claimantMilitaryPO": null,
           "claimantMilitaryPostalCode": null,
           "claimantState": "TX",
           "claimantZip": "78613",
           "dateRequestActioned": "2024-05-09T02:18:04-05:00",
           "dateRequestReceived": "2013-02-10T13:47:54-06:00",
           "declinedReason": null,
           "healthInfoAuth": "N",
           "poaCode": "083",
           "procID": "12072",
           "secondaryStatus": "Accepted",
           "vetFirstName": "Pat",
           "vetLastName": "Morris",
           "vetMiddleName": "H",
           "vetPtcpntID": "600043198"
       }
   ]
   

4. Adjust filters and resend as desired.

Screenshots

What areas of the site does it impact?

• Power of attorney requests (index)
• v2 staging docs

Acceptance criteria

• I added unit tests and integration tests for each feature (if applicable).
• No error nor warning in the console.
• Events are being sent to the appropriate logging solution
• Documentation has been updated (link to documentation)
• No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
• Feature/bug has a monitor built into Datadog (if applicable)
• If app impacted requires authentication, did you login to a local build and verify all authenticated routes work as expected
• I added a screenshot of the developed feature

Requested Feedback

N/A

[tycol7]

missed this test in #19268, so adding here.

[FonzMP]