Deleting team breaks the tasks still linked to it

[fm3]

When a team is deleted, tasks associated to it can no longer be loaded. The same may be true for other database entries. We need to develop a strategy for how to change the dependant entries.

[fm3]

There are a couple of options here

• Disallow deleting teams completely

• Disallow deleting teams if they are linked to any annotation, project or tasktype

• Delete annotations, projects and tasktypes linked to the team when deleting it

• Set team to null for annotations, tasktypes and projects (means only admin can see them, and nobody gets their tasks)
  → problem: they are no longer linked to an organization, meaning even the admin cannot access them. as good as deleting
  → todo: open tasks become inaccessible but are still listed for their owners (annotation access query needs to be adapted)

• Only “archive” the team (meaning it is not listed, and removed from users and datasets, but annotations, tasktypes and projects can still have it
  → todo: open tasks become inaccessible but are still listed for their owners (annotation access query needs to be adapted OR cancel them in the archiving call)
  → problem: user may be confused when editing task type / project that still have an archived team. May need warning message when viewing task type / project