Supporting extraAnnotions at pgbouncer deployment level

[amoghrajesh]

Adds support for integrating extraAnnotations in the pgbouncer deployment spec when defined in values.yaml during setup

closes: #27246

---

^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

[amoghrajesh]

@potiuk @jedcunningham can I get a review on this PR if you have some free time?

[jedcunningham]

How is this different than pgbouncer.podAnnotations?

[amoghrajesh]

@jedcunningham I was trying to cover up the tech debt due to thseparatePR: #27247
Not sure about the exact intention but looks like an effort to seperate the annotations into podAnnotations and extraAnnotations

[jedcunningham]

I don't see any reason to have 2 ways to set annotations on the pod, and podAnnotations is how it's done elsewhere. extraAnnotations is just used on our services.

I've marked that issue as closed by #30168. Thanks @amoghrajesh!