[addon-operator] Fix module re-enable using old values after disable

[riptide-01]

Overview

This PR fixes a bug where a module, when re-enabled after being disabled, incorrectly reused old values that were set before the disable operation.

Before:

alias dc="kubectl -n d8-system exec -it deployment/deckhouse -c deckhouse -- deckhouse-controller"

dc module enable test
dc module values test
internal:
  apiServers:
    - kube-apiserver-smyslov-master-0
  test: 2025-08-18 11:45:38.180898758 +0000 UTC m=+0.322006676
replicas: 1

dc module disable test
dc module values test
internal:
  apiServers:
    - kube-apiserver-smyslov-master-0
  test: 2025-08-18 11:45:38.180898758 +0000 UTC m=+0.322006676
replicas: 1

After:

alias dc="kubectl -n d8-system exec -it deployment/deckhouse -c deckhouse -- deckhouse-controller"

dc module enable test
dc module values test
internal:
  apiServers:
    - kube-apiserver-smyslov-master-0
  test: 2025-08-18 11:45:38.180898758 +0000 UTC m=+0.322006676
replicas: 1

dc module disable test
dc module values test
internal:
  apiServers: []
  test: ""
replicas: 1

What this PR does / why we need it

Without this fix, re-enabling a module could lead to unexpected behavior because it would restore outdated configuration values instead of starting with a clean state.

Special notes for your reviewer

• Changes were tested in the Kubernetes cluster manually.