fix: add podUpdatePolicy to all ComponentDefinition templates

[Alegrowin]

Summary

When podUpdatePolicy is not explicitly set in cmpd templates, the KubeBlocks operator defaults it to PreferInPlace after creation. This changes the apps.kubeblocks.io/immutable-hash annotation, causing the addon controller to mark ComponentDefinitions as Unavailable with "immutable fields can't be updated" on next reconciliation.

Changes

Adds podUpdatePolicy: PreferInPlace to all 122 ComponentDefinition template files across all addons, ensuring the hash is stable from creation.

Affected addons: apecloud-mysql, clickhouse, elasticsearch, etcd, falkordb, greptimedb, influxdb, kafka, llm, loki, mariadb, milvus, minio, mogdb, mongodb, mysql, nebula, neo4j, neon, opensearch, orchestrator, orioledb, polardbx, postgresql, pulsar, qdrant, rabbitmq, redis, risingwave, rocketmq, starrocks-ce, tidb, vanilla-postgresql, victoria-metrics, weaviate, xinference, yashandb, zookeeper

Verification

1. Install any addon (e.g. helm upgrade -i kb-addon-rabbitmq kubeblocks-addons/rabbitmq -n kubeblocks-system)
2. Check ComponentDefinition has podUpdatePolicy: PreferInPlace set: kubectl get cmpd <name> -o yaml | grep podUpdatePolicy
3. Verify hash remains stable across reconciliation cycles: kubectl get cmpd <name> -o jsonpath='{.metadata.annotations.apps\.kubeblocks\.io/immutable-hash}'

Companion PR

• fix: zero PodUpdatePolicy and PodUpgradePolicy in cmpdHash to prevent immutable-hash mismatch kubeblocks#10095: zeros PodUpdatePolicy/PodUpgradePolicy in cmpdHash() (root cause fix in the hash function itself)

[leon-ape]

It’s not necessary to explicitly set podUpdatePolicy in addon manifests after apecloud/kubeblocks#10095, because the actual compatibility issue is resolved by excluding these fields from cmpdHash().