TMSS-506: moved business logic into SchedulingUnitBlueprint class. Use it to send CannotProceed event.

TMSS-320: run create in an atomic trannsaction so django can continue in case an IntegrityError is raised. See: https://docs.djangoproject.com/en/3.1/topics/db/transactions/#controlling-transactions-explicitly

TMSS-320: copy dp feedback from input dp. The ingest subtask does not alter the feedback/dataproducts

TMSS-482: Add extended views for SU draft and blueprint that expand selected references and include them as single json blob. Refactor to avoid issues with circular imports.

TMSS-320: use UniqueConstraint to ensure that no duplicate task_drafts are created within one scheduling unit

TMSS-320: generate same SIP as for input dataproduct, but enriched with storageTicket and hashes for an ingest subtask output dataproduct

TMSS-320: removed TaskBlueprintSummary and SchedulingUnitBlueprintSummary which made it into master somehow via some merge? Anyway, they were obsolete, they are still obsolete

scheduling_unit_flow/qa_scheduling_unit_task allows to navigate the workflow steps and to get the current status

TMSS-320: added methods to get/compute the progress of a subtask, process_archive_information for a dataproduct, and to find the transformed_output_dataproduct for a given input dataproduct

This does not work on dev machines but it does work for docker deployment.
A better solution needs to be found to work with both.

TMSS-320: replaced FK by OneToOneField because a single dataproduct has a single archive info. renamed related_names. added ADLER32 hashtype