Add a task instance dependency for mapped dependencies

[stevenschaerer]

This closes#37091.

In particular, dynamically mapped tasks currently show as failed_upstream instead of skipped if some of the tasks that generate the mapping are skipped and the trigger rule is none_failed, all_done or similar.

This is because when trying to expand the mapped task, a failed and skipped mapped dependency behave identically and both result in a NotFullyPopulated being raised.

This PR introduces a new task instance dependency that sets a dynamically mapped task to skipped if any of the mapped dependencies are skipped (but not failed) and to upstream_failed if any of the mapped dependencies are failed. As such, an expansion of the mapped task is never attempted.

Before (from #37091):

After:

[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

[eladkal]

@stevenschaerer can you address the comments and rebase ?

[stevenschaerer]

@uranusjr Could you please review my latest changes and responses to your comments? Thanks!