trivy would not be auto re-created after deletion

[MinerYang]

If you are reporting a problem, please make sure the following information are provided:

Expected behavior and actual behavior:
trivy should be re-created after deletion , same as core, job service, exporter etc other components

Steps to reproduce the problem:

• deploy a harbor cluster with trivy
  kubectl apply -f my-full-stack.yaml
• delete trivy CR manually
  kubectl delete trivy harborcluster-sample-harbor-harbor -n cluster-sample-ns
• check if the trivy CR and related reousrces been recreated

ubuntu@miner:~$ kubectl get trivy -n cluster-sample-ns
No resources found in cluster-sample-ns namespace.

• check the harbor operator logs

ubuntu@miner:~$ kubectl logs -f harbor-operator-57986ddb6d-rhb4d -n harbor-operator-ns
2023-07-10T10:02:27Z	INFO	harbor-operator.controller	Reconcile is completed	{"controller": "harborcluster", "version": "dev", "git.commit": "none"}
2023-07-10T10:03:22Z	INFO	harbor-operator.controller	Object does not exists	{"controller": "trivy", "version": "dev", "git.commit": "none", "request": "cluster-sample-ns/harborcluster-sample-harbor-harbor"}
2023-07-10T10:03:22Z	INFO	harbor-operator.controller	Object does not exists	{"controller": "trivy", "version": "dev", "git.commit": "none", "request": "cluster-sample-ns/harborcluster-sample-harbor-harbor"}
2023-07-10T10:03:22Z	INFO	harbor-operator.controller	Object does not exists	{"controller": "trivy", "version": "dev", "git.commit": "none", "request": "cluster-sample-ns/harborcluster-sample-harbor-harbor"}
2023-07-10T10:03:22Z	INFO	harbor-operator.controller	Object does not exists	{"controller": "trivy", "version": "dev", "git.commit": "none", "request": "cluster-sample-ns/harborcluster-sample-harbor-harbor"}
2023-07-10T10:03:22Z	INFO	harbor-operator.controller	Object does not exists	{"controller": "trivy", "version": "dev", "git.commit": "none", "request": "cluster-sample-ns/harborcluster-sample-harbor-harbor"}

Versions:
Please specify the versions of following systems.

• harbor operator version: master

• harbor version: v2.6.2

• kubernetes version: 1.24.6

• Any additional relevant versions such as CertManager
  certmanager
  Additional context:

• Harbor dependent services:

  • Context info of postgreSQL
  • Context info of Redis
  • Context info of storage

• Log files: Collect logs and attach them here if have.

• Kubernetes: How Kubernetes access was provided (what cloud provider, service-account configuration, ...).