fix: upgrade bundled Kruise chart to v1.8.3

[loveRhythm1990]

Summary

• upgrade the bundled OpenKruise Helm Chart from v1.4.0 to v1.8.3
• bump the matrixone-operator Chart from 1.3.0-alpha.3 to 1.3.0-alpha.4
• package the local Kruise Chart before publishing or running repository E2E tests
• keep the matrixone-operator source code, container image, and kruise-api Go dependency unchanged

This fixes the Kruise daemon startup failure on Kubernetes 1.34/containerd 2.x, where Kruise v1.4.0 attempts to use the removed CRI v1alpha2 ImageService.

Closes #609.

Upgrade behavior

The target release performs an in-place Helm upgrade:

• update Kruise CRD definitions in place
• roll the Kruise manager and daemon from v1.4.0 to v1.8.3
• preserve existing MatrixOne CRs, workloads, Pods, PVCs, and data
• keep the matrixone-operator image at matrixorigin/matrixone-operator:1.2.0-alpha.5

E2E scope

Two E2E paths are relevant:

1. Manual upgrade E2E: validated the full v1.4.0 to v1.8.3 in-place upgrade, workload identity preservation, SQL compatibility, rollback, and a second upgrade.
2. Repository CI E2E: historically installed Kruise v1.4.0. This PR updates it to package and install the local Kruise v1.8.3 Chart, so CI tests the exact code under review before v1.8.3 exists in the MatrixOrigin remote Chart repository.

The github.com/openkruise/kruise-api v1.4.0 dependency is intentionally unchanged. It controls compile-time API types, not the Kruise controller image deployed in E2E.

Validation completed

• make verify
• actionlint .github/workflows/release_chart.yml
• Helm dependency, lint, package, and template checks
• Kubernetes 1.34.8/containerd 2.3.1 reproduction and recovery with Kruise v1.8.3
• Kubernetes 1.28.13/containerd 1.7.18 full MatrixOne upgrade, 47 SQL probes, workload/PVC identity checks, rollback, and second upgrade

Follow-up

The non-blocking StorageClass watch/RBAC log observation is tracked separately in #610.

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →