[Project] Prevent changes to survey from making data inaccessible

[gino-m]

We currently show BSWs (Big Scary Warnings) in most cases when the survey organizer is about to do something destructive. We should instead prevent data loss from occurring by flagging fields as deleted and prevent changes which would break data consistency. Several cases where data would be corrupt:

Destructive action	New strategy	Android app	Survey editor (web)	Main dashboard (web)
Delete job	Flag jobs as "deleted"	Hide deleted	P0: Hide deleted P2: Show deleted and allow un-delete	P0: Hide in job list P2: Show as "deleted" in job list
Delete task	Flag tasks as "deleted"	"	"	Only show in submission with related data
Delete multiple choice option	"	"	"
Change to incompatible task type	Disallow change once published	n/a	n/a	n/a
Edit question / task instructions	TBD
Edit task	TBD
Edit LOI location	TBD
Edit multiple choice options	TBD

[gino-m]

@rfontanarosa @shobhitagarwal1612 Any edge cases I'm missing here?

[kenstershiro]

@gino-m is this still considered a P-0? The description table is incomplete, if there are specific warnings that are higher priority can we create separate tasks for them, so that those can be actioned meanwhile? Otherwise I can lower the priority on this.