Consider to support install wait for helm chart

[qiaoleiatms]

Feature Request

Describe the problem you need a feature to resolve.

Sometimes, we need to represent the final status of the helm chart installation to the CR, for example, imagine here's an App resource, which will install a K8s Deployment from the corresponding helm chart, we want to see the status of App to deployed only when all the pods of the deployment is in running status

Describe the solution you'd like.

Consider to support get annotation helm.sdk.operatorframework.io/install-wait from App CR, if it exists and has a value to true, we can mark the InstallOption to wait
https://github.com/yilims/operator-sdk/blob/308b320f3d4f00d1994a16f5f5d52ba902f21a16/internal/helm/controller/reconcile.go#L244

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.