[DAR-5014][External] Better error messaging when importing to items not ready to receive annotations

[JBWilkie]

Problem

This ticket tackles 2 problems:

• 1: When importing annotations to items not ready to receive them, imports would fail without any error handling. These are items in the uploading, processing, error, and archived statuses
• 2: When importing NifTI annotations, if any item in the dataset was not in a state to receive annotations (even an item not targeted by the import), the import would fail without any error handling. This is happening due to the fetch_remote_files() call in _get_remote_files_that_require_legacy_scaling() not filtering for item status, then trying to retrieve slot information

Solution

• 1: If an import job is trying to import annotations to item(s) not ready to receive them, we raise an error and display which items are affected and what statuses they are in
• 2: When importing NifTI annotations, we only retrieve items in valid import statuses in the _get_remote_files_that_require_legacy_scaling() function. If there are items not ready to receive annotations, they will be found later in the import flow by _get_remote_files_ready_for_import()

Changelog

Better error handling and messaging when importing annotations to items not ready to receive them

[linear]

DAR-5014 BUG: Refine error messaging for when importing annotations to non-processed/error files

[dorfmanrobert]

These are workflow statuses not processing statuses right? PR description mentions uploading, processing, error, and archived; is that what should be used here?

[JBWilkie]

This is the status that list_items returns. In the backend, this is GeneralStatus, so it accounts for processing status

We need to use this status type, because list_items doesn't allow filtering based on processing status

[dorfmanrobert]

Gotcha thanks, I guess it would be nice to have types/objects that can be used for these but maybe a separate piece of work