Add wait mechanism into linkerd-crds Helm chart

Nobody has claimed this yet.

### What problem are you trying to solve?

After the split of crds and control-plan helm charts in https://github.com/linkerd/linkerd2/issues/6620, there is no mechanism for how to wait for crds to be present in the cluster when installing in an automated way.

For example, when installing both charts using Terraform Helm provider there is no deterministic approach how to detecting if crds are present in the cluster and subsequent control-plane installation could fail.

### How should the problem be solved?

Kubernetes Job could be added that will check the Kubernetes API for CRDs presence and its status. Then Helm release could leverage [`wait_for_jobs` ](https://registry.terraform.io/providers/hashicorp/helm/latest/docs/resources/release#wait_for_jobs) attribute.

### Any alternatives you've considered?

N/A

### How would users interact with this feature?

_No response_

### Would you like to work on this feature?

maybe

Start by reviewing the split between the CRD and control-plane Helm charts described in issue #6620, then read the Kubernetes Job and Terraform Helm provider wait_for_jobs references mentioned here. Done means the linkerd-crds chart checks that its CRDs are present and ready so a subsequent control-plane installation can wait deterministically.

Written by the indexing model from the issue text.