chore: bump kubeovn-operator-crd chart to 1.14.10-dev.2

[starbops]

Problem:

We currently couple the kubeovn-operator and kubeovn-operator-crd charts, so it's impossible to use different versions of them. As a result, we need to bump the kubeovn-operator-crd chart version to match kubeovn-operator's.

Solution:

Bump the kubeovn-operator-crd chart version

Related Issue(s):

harvester/harvester#9787

Test plan:

Additional documentation or context

[w13915984028]

LGTM, thanks for the quick fix.

[Copilot]

Pull request overview

This PR bumps the kubeovn-operator-crd Helm chart version to align with the kubeovn-operator chart version, as both charts are currently coupled and must use the same versions. The chart version is incremented from 1.14.10-dev.0 to 1.14.10-dev.2, and the appVersion is bumped from v1.14.10-dev.0 to v1.14.10-dev.1.

Changes:

• Updated chart version from 1.14.10-dev.0 to 1.14.10-dev.2
• Updated appVersion from v1.14.10-dev.0 to v1.14.10-dev.1

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The appVersion (v1.14.10-dev.1) is incrementing to dev.1 while the chart version is jumping to dev.2, creating a version mismatch. Based on the kubeovn-operator chart which has both version and appVersion at the same dev level (1.14.10-dev.2 and v1.14.10-dev.1 respectively), this appears correct. However, the version number jump from dev.0 to dev.2 suggests dev.1 was skipped. Consider verifying if the version number progression is intentional or if an intermediate version was missed.