Handle errors from exif-api

[nathanielrindlaub]

exif-api sometimes returns errors, which we currently do not handle. Instead, error messages get treated like they're exif data and added to the metadata payload we submit to createImage():

            "md": {
                "Bucket": "animl-images-ingestion-prod",
                "Key": "batch-fc20b725-e65d-4f30-b61e-d050a27cb2a1/SH2_2/113EK113/03300262.JPG",
                "errors": [],
                "FileName": "03300262.jpg",
                "batchId": "batch-fc20b725-e65d-4f30-b61e-d050a27cb2a1",
                "message": "S3 object does not exist, is empty, or access denied",  // this is the error message from exif-api
                "FileTypeExtension": ".jpg",
                "Make": "unknown",
                "MIMEType": "image/jpeg",
                "SerialNumber": "unknown",
                "ProdBucket": "animl-images-serving-prod",
                "Hash": "b040d0103782d6d7c59054d557c5d19b",
                "ImageBytes": 904827,
                "Path": "SH2_2/113EK113/03300262.JPG"
            }

Ideally, we would still create an imageAttempt record and then an imageError on the animl-api side so that users have some indication that there was an error with that image. I think this should be possible by passing the error into the errors array of the metadata we post to createImage(). See this line in animl-api to see how that would get handled on the API side.