change submission status checking to handle out of order xml

[mrotondo]

Link to pivotal/JIRA issue

• https://codeforamerica.atlassian.net/browse/FYST-1733

Is PM acceptance required? (delete one)

• Yes - don't merge until JIRA issue is accepted!

Reminder: merge main into this branch and get green tests before merging to main

What was done?

• This year, we've seen MeF submissions-status API responses that include "out of order" submissions statuses for a few states. That is, the XML document we receive includes "Received by State" after "Acknowledgement Received from State". Because we were previously assuming that we would always see the most "recent" or furthest-progress status at the top of the list, we were only looking at first node in the XML document corresponding to each submission ID we poll for. Thus, we have been failing to process a bunch of submissions out of the transmitted state.
• This PR changes our submission status checking to look through the whole list of submission statuses for each submission ID we are polling for, first looking for any status that would transition the submission to ready-for-ack, then any which would keep it in transmitted (and then failing if neither are found, though we should always find the node that marked the submission as transmitted in the first place).

How to test?

• There are submissions on demo that are stuck in this state, so we can do acceptance by checking to see whether they proceed to :ready-for-ack and :accepted after this is merged to main and the cron job runs the poll service.

[github-actions]

Heroku app: https://gyr-review-app-5499-bb2a2869ffbe.herokuapp.com/
View logs: heroku logs --app gyr-review-app-5499 (optionally add --tail)

[embarnard]

Looks good to me!