Overview

Add a more informative status field to annotation projects
Migrate from the ready field to a status field
Set statuses correctly in upload processing

Checklist

• Description of PR is in an appropriate section of the changelog and grouped with similar changes if possible
• Swagger specification updated
• New tables and queries have appropriate indices added (N/A)
• Any content changes are properly templated using BUILDCONFIG.APP_NAME
• Any new SQL strings have tests
• Any new endpoints have scope validation and are included in the integration test csv

Demo

Statuses as set by raising exceptions in the appropriate sections of the upload batch process:

Notes

Error handling does not encompass larger scale batch issues (unable to contact API, etc), since we don't have a good way of handling that right now. This should be handled in a later issue

Testing Instructions

• build your batch jar
• build your batch container
• run migrations
• start the API server, etc.
• start the annotate frontend on the accompanying annotate branch
• create a project with a small upload to make things to quickly
• find the upload id in your database: select id from uploads where annotation_project_id = '<annotation_project_id>';
• run the batch command to ingest the upload: ./scripts/console batch 'AWS_BATCH_JOB_ATTEMPT=3 rf process-upload 819c2ce5-e48a-40c3-8a27-f274b1ec4e59'
• refresh the project list and verify that the status is set to "ready" as expected
• stick a normal exception inside the main try catch block, rebuild the batch container, and re-run the batch command. Verify that it sets the status to IMAGE_INGESTION_FAILURE
• stick a TaskGridError there instead and verify it sets the status to TASK_GRID_FAILURE

Closes https://github.com/raster-foundry/annotate/issues/670