unable to manage helm chart outside of k0sctl

I just upgraded a cluster using k0sctl `v0.12.4` where I initiatilly deployed a helm chart like this:

```yaml
extensions:
helm:
charts:
- name: cilium
chartname: cilium/cilium
version: 1.11.0
values:
```

I'm trying to upgrade the chart to version `1.11.1` but k0sctl will always deploy the same values and the same version as provided during cluster creation.

I have observed the following:

1. if I change the chart version and values in the k0sctl file, it gets ignored. No `helm upgrade` is run
2. if I run `helm upgrade` myself with new values and version before (1) and then run the apply k0sctl config, the helm chart is downgraded to the version and config provided during installation
3. if I delete the chart config from k0sctl, it happens the same as in (2)

Not sure if it's relevant, but I'm using dynamic configuration. I've not tried to change the `k0s.k0sproject.io/v1beta1/clusterconfigs` resource, as I don't know the implications of doing it directly vs `k0sctl apply`. Is this what I should be doing?

Another possibility I considered was editing the clusterconfig and remove the cilium chart altogether, but I don't want cilium removed for obvious reasons and I don't know if that would uninstall the chart

Reproduce the behavior with the extensions.helm.charts configuration, changing the Cilium version and values before running k0sctl apply. Trace how k0sctl apply and the clusterconfigs resource manage chart state, including removal, and define done as applying updated chart settings without silently restoring the installation-time values or version.

Written by the indexing model from the issue text.