fix(api): accept scalar dynamicConfig values

[bmorton]

Problem

Applying a TemporalCluster with scalar dynamicConfig values fails validation:

TemporalCluster ... is invalid: spec.dynamicConfig.values.activity.enableStandalone[0].value:
Invalid value: "boolean": ... in body must be of type object: "boolean" ...

DynamicConfigValue.Value was a runtime.RawExtension, which controller-gen renders as type: object + x-kubernetes-preserve-unknown-fields: true. The apiserver's structural-schema validation then rejects any scalar (bool/number/string), so keys like history.enableTransitionHistory, history.enableChasm, and activity.enableStandalone (which take boolean values) cannot be applied.

Fix

Switch the field to schemaless JSON:

// +kubebuilder:validation:Schemaless
// +kubebuilder:pruning:PreserveUnknownFields
Value apiextensionsv1.JSON `json:"value"`

The generated CRD now emits x-kubernetes-preserve-unknown-fields: true without type: object, so scalars, objects, and arrays are all accepted. The consumer keeps reading v.Value.Raw, so dynamic-config rendering is unchanged.

Changes

• api/v1alpha1/shared_types.go — runtime.RawExtension → apiextensionsv1.JSON + Schemaless.
• Regenerated CRD manifests, Helm chart, and API reference docs.
• Added an envtest regression in temporalcluster_controller_test.go that creates a cluster with scalar dynamicConfig values (bool/number/string) against the real CRD.

Verification

• make build, make lint (0 issues)
• go test ./internal/temporal/... ./internal/controller/... (incl. new envtest) — pass
• WASM preview build compiles (API stays WASM-safe)