18400 chart custom pod annotations

[wc-s]

closes: #18400

The change allows adding different custom pod annotations to the different airflow components (whereas the current chart can only add the same set of custom pod annotations to all airflow components).

Some notes:

• The per-component pod annotations take precedence over the global pod annotations injected via .Values.airflowPodAnnotations
• I've only added it to components that already currently support airflowPodAnnotations, which excludes redis etc. I don't know why we have airflowPodAnnotations in some components but not in others, but I want to just continue to convention to keep things clean.
• Added annotations test for triggerer as well.
• Added 2 new test cases, one to test the basic functionality, and one to test the precedence. There are some copy-paste between the two tests but I think there is no need for further abstraction or code-reuse because YAGNI.
• Also refactored the existing ServiceAccount annotations test to make it IMO simpler and more readable.

---

^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code change, 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 UPDATING.md.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contribution Guide (https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst)
Here are some useful points:

• Pay attention to the quality of your code (flake8, mypy and type annotations). Our pre-commits will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it’s a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: [email protected]
  Slack: https://s.apache.org/airflow-slack

[github-actions]

The PR is likely OK to be merged with just subset of tests for default Python and Database versions without running the full matrix of tests, because it does not modify the core of Airflow. If the committers decide that the full tests matrix is needed, they will add the label 'full tests needed'. Then you should rebase to the latest main or amend the last commit of the PR, and push it with --force-with-lease.

[jedcunningham]

Giving CI another shot...

[wc-s]

Thanks for the review.

What's up with the pipeline? Seems like flakiness to me, and the helm test failure happens to your 1.20 docs-only change as well.

[jedcunningham]

Yeah sorry, it's been particularly painful the last few days unfortunately. I'll try again now, and I can run the full suite locally if that still doesn't do it.

[potiuk]

Yeah. I hope (🤞 ) We finally fixed all the "major" flakiness problems - so the last error here is the real failing test :)

[potiuk]

Close/reopen to rebuild. the Helm Chart might however still hang (and that might be a general problem) - let's see

[wc-s]

The helm chart unit test passes!

(I do think it's general flakiness rather than real test failures.. don't know enough about the CI tests to know why, maybe because of the parallel execution.)

[wc-s]

Are we ok with merging this, given that the temperamental test is luckily in a passing state? 😆

[potiuk]

Well. I would not say lucky. We are really just about to reach the state of "back to green" on main. I think there is one very intermittent issue currently that I know about :D

[boring-cyborg]

Awesome work, congrats on your first merged pull request!