[Bug Report]: clusterExtensionTypeName issue in the template

### cli command

az partnercenter marketplace offer plan technical-configuration package add

### Extension version

0.2.7

### Describe the bug

We found a new issue when promoting new versions to the Marketplace using the extension. We got the following error when deploying a CNAB solution in Azure

> Extension type '--payloadId' is not supported in region 'westus2' for cluster type: ManagedClusters. Please refer to https://aka.ms/k8s-extensions-list-cluster for a list of supported extension types for this cluster.

When investigating the error, we found that the template the portal is trying to deploy has the following information:

> "variables": {
> "clusterExtensionTypeName": "--payloadId",

However, the template we have locally before running the "az partnercenter marketplace offer plan technical-configuration package add" command includes the following, similar to [what the examples include](https://github.com/Azure-Samples/kubernetes-offer-samples/blob/main/samples/k8s-offer-azure-vote/mainTemplate.json#L153):

> "variables": {
> "clusterExtensionTypeName": "DONOTMODIFY",

and AFAIK, that value is overwritten during the "package add" command [using the cluster-extension-type parameter](https://github.com/Azure/partnercenter-cli-extension/blob/22ff477385bc230ced421d00fac5f76b5802a3f5/doc/how_to_managed_k8s_apps.md?plain=1#L76). Is this assumption correct?

Thanks

### To reproduce

Try to deploy the Bitnami Redis CNAB package

https://azuremarketplace.microsoft.com/en-us/marketplace/apps/bitnami.redis-cnab

### Code snippet

```Bicep

```

### Relevant log output

```Shell

```

Start with the package add command and the guidance in doc/how_to_managed_k8s_apps.md, especially the cluster-extension-type parameter. Compare the generated template with the examples in samples/k8s-offer-azure-vote/mainTemplate.json and reproduce using the Bitnami Redis CNAB package. Done means the generated clusterExtensionTypeName reflects the supplied parameter and the deployment no longer uses --payloadId.

Written by the indexing model from the issue text.