Find your committee view improvements

[exalate-issue-sync]

Several improvements to the get-available-committee endpoint logic were identified when conducting analysis for ticket 3060 investigating occasional slowness for this endpoint on the Find your committee screen after sign-on.

These fixes will help improve the requests being made to the openfec api:

1. We are currently sending duplicate requests for processed and (conditionally) raw data. The duplicate requests are being generated by the raise_if_cannot_create_committee_accountfunction that retrieves the committee email information in order to validate it. We should however be able to use the email information in data that was already retrieved in most cases.
2. remove the committee_id query param in the get_processed data request since it is already set as a path param.
3. add the per_page param to the get_raw_data request to limit the record count coming back from openfec (since we only need the first one and it is defaulting to 20).
4. add a descending sort param on date so that we get the most recent record for raw data (per documentation -receipt_date https://api.open.fec.gov/developers/#/filings/get_v1_filings_ )

QA Notes

null

DEV Notes

null

Design

null

See full ticket and images here: FECFILE-3104

[exalate-issue-sync]

akhorsand commented: [~accountid:712020:005cf740-faa3-4d67-baff-f316981bdc9f] [~accountid:712020:2a1493e5-adee-45bd-b27e-868a5c8d3f62] can this go in refinement? Looks ready for me.

[exalate-issue-sync]

David Heitzer commented: [~accountid:61b0b42cd5986c006a9e1c94] I agree but will let [~accountid:712020:2a1493e5-adee-45bd-b27e-868a5c8d3f62] have the final say.