Fail the task if the xcom sidecar container does not start for a long time

[jhongy1994]

This PR fixes XCOM_sidecar_container not started results in long running DAG
Closes: #38115

The following operators are affected:

• KubernetesPodOperator

Although startup_timeout_seconds is the timeout for the pod start, there is no parameter to set the timeout for the sidecar container in KubernetesPodOperator. Therefore, I have used startup_timeout_seconds for xcom sidecar container too.

Instead of above approach, I have also considered the following alternatives:

• Adding a new parameter to KubernetesPodOperator to set the timeout for the XCOM container.
• Raising an Exception if attempt > 1 instead of using a timeout.

If you have any better suggestions, please let me know.

---

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

[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 Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, 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.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

[amoghrajesh]

@jhongy1994 good work on your first PR. A few review comments

[amoghrajesh]

Can we just dump the events as well? That would be a better indicator than users manually checking in k8s

[amoghrajesh]

Can we add test cases for this change? Like basically call this, sleep for certain seconds and then check if the exception came up

[romsharon98]

I agree with your choice to use startup_timeout_seconds 😄

[hussein-awala]

A small nit, LGTM

[jhongy1994]

@hussein-awala Thank you for your review!
I've applied the changes you suggested.

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions.

[injae-kim]

gentle ping to reviewers @amoghrajesh, @romsharon98, @hussein-awala 😃can we merge this PR?

[eladkal]

@jhongy1994 can you rebase and resolve conflicts?

[jhongy1994]

@eladkal thanks for your feedback!
I see that the issue has been resolved through another PR(#42504). I'll close this one to avoid duplication. Looking forward to contributing more in the future!