Don't disable monitors before after delete hook run

[timmilesdw]

Overview

Defer stopping Kubernetes monitors for modules scheduled to be disabled. In converge phase, only disable schedule bindings; keep Kubernetes watchers alive until afterDeleteHelm runs during DeleteModule. Full hook disabling still happens right after afterDeleteHelm.

What this PR does / why we need it

• Previously, converge disabled all module hooks (including Kubernetes monitors) immediately for modules in ModulesToDisable. As a side effect, afterDeleteHelm hooks received empty snapshots because monitors were already stopped.
• This PR:
  • Changes converge to disable only schedule bindings for modules to disable.
  • Leaves Kubernetes monitors running so DeleteModule can execute afterDeleteHelm with populated snapshots.
  • Keeps the existing cleanup: DisableModuleHooks is still invoked in DeleteModule right after afterDeleteHelm, stopping both schedules and monitors.

Why needed:

• Restores documented behavior that afterDeleteHelm hooks receive snapshots of their Kubernetes bindings.
• Unblocks reliable cleanup logic (e.g., deleting CRs/secrets) during module disable.
• Minimizes event noise by keeping schedules off while preventing data loss for snapshots.