Handle Hybrid executors for running task logs

[dmelchor-stripe]

Using Hybrid executors where one of them is a Kubernetes-based executor (but not the first one) breaks live logs since we only try to fetch k8s pods logs if the default executor happens to be the Kubernetes executor. This PR fixes it.

Note: it's my first PR and I probably don't have time to set up the whole testing environment. If you consider this change requires thorough testing please FFT to close this and revisit at a further date (just wanted to flag this)

[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: [email protected]
  Slack: https://s.apache.org/airflow-slack

[o-nikolas]

We already have an extensively tested and iterated on fix for the same issue here: #45631

I'll close this one in favour of the existing one. Thanks for the contribution though!