helm升级到2.5.1 报错

命令：
```shell
helm upgrade notification-manager --set kubesphere.enabled=true --set notificationmanager.sidecar.tenant.resources.limits.cpu=500m --set notificationmanager.sidecar.tenant.resources.limits.memory=500Mi --set notificationmanager.sidecar.tenant.resources.requests.cpu=500m --set notificationmanager.sidecar.tenant.resources.requests.memory=500Mi --set operator.containers.proxy.image.repo=harbor-k8s.net/kubesphere/kube-rbac-proxy --set operator.containers.operator.image.repo=harbor-k8s.net/kubesphere/notification-manager-operator --set notificationmanager.image.repo=harbor-k8s.net/kubesphere/notification-manager --set notificationmanager.sidecar.image.repo=harbor-k8s.net/kubesphere/notification-tenant-sidecar -n kubesphere-monitoring-system ./notification-manager.tgz

```
错误：
```shell
Error: UPGRADE FAILED: cannot patch "notification-manager" with kind NotificationManager: NotificationManager.notification.kubesphere.io "notification-manager" is invalid: [spec.sidecars.tenant.name: Required value, spec.sidecars.tenant.type: Required value]
```

Start with the supplied helm upgrade command and inspect the notification-manager chart and NotificationManager resource validation related to the reported required fields. Reproduce the failure in a Kubernetes environment; done means the upgrade completes without the spec.sidecars.tenant.name and spec.sidecars.tenant.type validation errors.

Written by the indexing model from the issue text.