podMonitor name conflicts for multiple releases in the same namespace

[LoveEachDay]

Describe the bug Install two releases of pulsar cluster with podMonitor enabled in the same namespace will fail.

To Reproduce Steps to reproduce the behavior:

1. install release test-1 in default namespace helm install test-1 apache/pulsar --set broker.podMonitor.enabled=true this will success
2. install release test-2 in default namespace helm install test-2 apache/pulsar --set broker.podMonitor.enabled=true This will fail due to the following error:

Error: INSTALLATION FAILED: rendered manifests contain a resource that already exists. Unable to continue with install: PodMonitor "pulsar-broker" in namespace "default" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-name" must equal "test-2": current value is "test-1"

Expected behavior Expect the second installment will also be successful.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information): apache/pulsar chart version: 2.9.2

Additional context Add any other context about the problem here.

[LoveEachDay]

/assign @LoveEachDay