fix: partners seeing all listings in list

[emilyjablonski]

This PR addresses #1014

• Addresses the issue in full
• Addresses only certain aspects of the issue

Description

The partners list was no longer filtering by jurisdiction. The cause was that for the map, we changed the structure of the combined list to send filter parameters in the body, which updated some of the swagger for the filters, but we didn't update the generic list to send parameters in the body as well.

How Can This Be Tested/Reviewed?

Create a partner and assign them only to some jurisdictions / listings. Ensure they only see those listings in the list.

Author Checklist:

• Added QA notes to the issue with applicable URLs
• Reviewed in a desktop view
• Reviewed in a mobile view
• Reviewed considering accessibility
• Added tests covering the changes
• Made corresponding changes to the documentation
• Ran yarn generate:client and/or created a migration when required

Review Process:

• Read and understand the issue
• Ensure the author has added QA notes
• Review the code itself from a style point of view
• Pull the changes down locally and test that the acceptance criteria is met
• Either (1) explicitly ask a clarifying question, (2) request changes, or (3) approve the PR, even if there are very small remaining changes, if you don't need to re-review after the updates

[mcgarrye]

question: I wasn't able to review the other map PRs, was it discussed that we were switching GET endpoints to POST? This pattern diverges from RESTful practices and the rest of our system so am wondering what the reasoning behind it was

[mcgarrye]

Looks good!

[ludtkemorgan]

Nice quick fix! I do notice that if you go to a listing you don't have permission to see in staging it sends you to a fully white page rather than an error page. That is a bug in main as well though so we don't need to tackle it as part of this.

[emilyjablonski]

@mcgarrye https://github.com/metrotranscom/doorway/pull/899/files#r1839233455 Indeed! This was actually Yazeed's work, filtering listings by IDs was too large to send as a query