Update ES&S CVR parsing to support latest format (as seen in Washington's Thurston County)

[arsalansufi]

https://votingworks.slack.com/archives/C013V6CT9H9/p1708479181164829

Washington has since deleted the relevant audit data, so we don't have access to a sample file from Thurston County. But reading the above Slack post, the file format appears to mirror the latest file format seen in Rhode Island, which we've accounted for in our batch inventory CVR parsing logic. The new format is actually simpler. The CVR file contains all the relevant info that we need; information is no longer spread across a CVR file and one or more ballots files.

We should update our ballot comparison audit CVR parsing logic to handle this new file format, too.

Sample file from Rhode Island: COVPPPTest.xlsx

[ginvdr]

WA reached out this week to make sure this is on our radar and requested that it be complete by the end of June. Some files can be found here: https://votingworks.slack.com/archives/CKCVA0F9S/p1715087828353039. One is a CVR and the other is the steps Thurston has been taking to convert them to the old format themselves.

[arsalansufi]

These ES&S files are supported via the combo of:

• Update mistaken assumption re type-1 and type-2 ES&S CVR ballots files #1950
• ES&S CVR parsing: Allow "hinting" which file is the CVR file by changing the file name #1952
• Hotfix: Expect more possible metadata columns when parsing ES&S CVRs #1954
• ES&S CVR parsing: Protect against unknown columns in CVR file #1960

We could still do more to improve, but I'm going to open a new issue to track that work