[ADD] cetmix_tower_jet_isolation: add uninstall hook to reset isolation data

When the module is uninstalled Odoo does not drop the columns it added to
cx.tower.jet.template, so existing records may keep isolation_mode=True and
silently continue to restrict commands/plans even with the module gone.

The new uninstall_hook resets all isolation-related fields to their neutral
state (isolation_mode=False, forced_applicability=False, both tag M2M cleared)
on every jet template before the module is removed from the registry.

* hooks.py            - new file with uninstall_hook function
* __init__.py         - import hooks so Odoo can resolve the hook entry point
* __manifest__.py     - register uninstall_hook key

Author: marionumza

cetmix_tower_jet_isolation/__init__.py

@@ -1,2 +1 @@
-from . import models
-from . import wizards
+from . import hooks, models, wizards

cetmix_tower_jet_isolation/__manifest__.py

@@ -15,4 +15,5 @@
     ],
     "installable": True,
     "license": "AGPL-3",
+    "uninstall_hook": "uninstall_hook",
 }

cetmix_tower_jet_isolation/hooks.py

@@ -0,0 +1,17 @@
+def uninstall_hook(env):
+    """Reset isolation fields on all jet templates when the module is uninstalled.
+
+    Odoo does not drop columns when a module is uninstalled, so any templates
+    that had ``isolation_mode`` enabled would still carry the value ``True``
+    in their row.  When the module is re-installed (or the column is somehow
+    still read) those stale values would silently reactivate the restriction
+    logic.  Resetting them here ensures a clean state.
+    """
+    env["cx.tower.jet.template"].search([("isolation_mode", "=", True)]).write(
+        {
+            "isolation_mode": False,
+            "forced_applicability": False,
+            "forced_command_tag_ids": [(5,)],
+            "forced_plan_tag_ids": [(5,)],
+        }
+    )