Add active_deadline_seconds parameter to KubernetesPodOperator

[amoghrajesh]

Building on top of #31146 to introduce the active_deadline_seconds for airflow KPO launched job pods.

---

^ 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.

[potiuk]

Needs conflict resolution and fixes in tests ...

[amoghrajesh]

@potiuk I fixed the tests as well as rebased it. Can you take a look when free?

[hussein-awala]

I pushed a commit hoping it might fix the failed test. LGTM

[amoghrajesh]

@hussein-awala seems like the commit didn't do the trick here. I pushed a new fix now, might just do the trick now

[potiuk]

Nope. Seems like it break our K8S tests. FYI. There is a recipe how to setup the environment for K8S tests locally with breeze including step-by-step explanation and example (and Breeze's k8s is really a wizard-like setup that hand-holds you while setting the environment up).

https://github.com/apache/airflow/blob/main/TESTING.rst#kubernetes-tests

[hussein-awala]

🎉

[amoghrajesh]

Silly mistake by me. Thanks Hussein!

[andyfcx]

Thanks @amoghrajesh