first pass at keeping overrides on face delete - should at least stop code crashing if you try to delete faces from DB and they still had a matching override

TODO

@@ -1,14 +1,14 @@
 ## GENERAL
-    * on viewer: 
-        - allow face to be used to:
-            [DONE] - create person
-            [DONE] - add to existing person
-            [DONE]   --> can choose to do AI search (for these 2 options)
-            [DONE] - ignore/not a face/too young 
-            [DONE] - redraw 'ignore's as a greyed out box?
-            [DONE] - menu should only allow override IF we have put override on...
-            all NMO's need to handle delete data and rebuild / allow recreation of content form FS (not just test, it causes a bug now / db constraint violation)
-                --> need to test the 'override' when we re-ai-match (AFTER re-build from FS)
+	* need force scan on a file as an option in GUI (to test below)
+
+	* keep overrides across 'deletes/rescans'
+		[DONE] - when we delete/force a full scan then move overrides into disconnected* tables
+		[PARTIAL] - when an individual face is deleted - need to keep any associated override
+				code is [DONE]
+				TEST! (no way to force a delete via gui as yet)
+		- when we scan a new face, we need to see if there is a matching override, if so, add override back & delete disc*
+		- TEST (add an override, delete refimg, re-add refimg & re-scan)
+		- TEST (forcescan job)
 
     * should I change the rotation code to use that jpeg util to reduce/remove compression loss?