Handle country code geocoding errors

[TaiWilkin]

Overview

Submitted facilities are frequently throwing the country code error,
which indicates that the geocoding process has returned a result that
doesn't contain the country which the contributor has submitted for the
facility.

There are two primary instances where this is occurring:

1. The returned geocoding result is imprecise and contains no country
   code at all. In this case, we will now accept this as a valid result.

2. There are multiple results returned, and although the top result
   has an invalid code, another result contains the correct country code.
   In this case, we will now select the result with the correct country
   code. (If there are both a result with a correct country code and an
   inexact result, we prefer the correct country code.)

We will still return a geocoding error if all results include
non-matching country codes.

Connects Client #62

Notes

I added additional mock data for geocoding responses in the test suite.

Testing Instructions

• These directions assume that ./scripts/resetdb has been run.
• Run ./scripts/server and upload facilities which previous threw geocoding errors.
  oar-country-geocode-errors.csv
• Process the facilities.

./scripts/manage batch_process --list-id 16 --action parse
./scripts/manage batch_process --list-id 16 --action geocode
./scripts/manage batch_process --list-id 16 --action match

• Confirm that the facilities have been successfully geocoded.
• Submit one or more of the addresses (with new names) via the API. Confirm that they have been successfully geocoded.

Checklist

• fixup! commits have been squashed
• CI passes after rebase
• CHANGELOG.md updated with summary of features or fixes, following Keep a Changelog guidelines

[caseycesari]

Working well. Nice, clean implementation function.

[TaiWilkin]

Thank you for reviewing!