Fix: enqueue in updating secret

[jamshidi799]

Add enqueueForPrometheusNamespace to secret update handler
It will fix #6309

Type of change

What type of changes does your code introduce to the Prometheus operator? Put an x in the box that apply.

• CHANGE (fix or feature that would cause existing functionality to not work as expected)
• FEATURE (non-breaking change which adds functionality)
• BUGFIX (non-breaking change which fixes an issue)
• ENHANCEMENT (non-breaking change which improves existing functionality)
• NONE (if none of the other choices apply. Example, tooling, build system, CI, docs, etc.)

Verification

Please check the Prometheus-Operator testing guidelines for recommendations about automated tests.

Changelog entry

Please put a one-line changelog entry below. This will be copied to the changelog file during the release process.

Add enqueueForPrometheusNamespace in secret update handler

[haanhvu]

Thanks for the PR! Do you think we need an e2e test case to replicate the issue? 🤔

[simonpasquier]

Ideally we'd need an e2e test to verify this but it's a bit more involved. I also think that we should reduce code duplication since all controllers have similar patterns for configmap/secret handlers but again it doesn't need to be in this be in this PR.
TL;DR: I'm fine merging as-is but I'll create more issues to follow-up.

[jamshidi799]

I'm interested in working on these code duplication as well