Speed up nested TaskGoups

[MarosMK]

This PR aims to speed up nested TaskGroups. During the checks in conditions the Task won't have to go into 'depth' to figure out the group_id.
This affects particularly cases where there is deep nesting of TaskGroups.

[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 (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.
  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

[uranusjr]

How much speedup does this produce? The task_group attribute is public and may potentially change and cause breakage too easily. If the main slowdown is from child_id calculation, it may be a better idea to cache at that level instead.

[MarosMK]

@uranusjr
The code changes were updated (no caching of group_id) so hopefully there is now less risk at stake and the speedup is the same as before.
For the time improvement, if we take nested groups of 3 (each task has 3 child tasks) and we go into 'depth' of 6 layers, the dag loading is faster by 7.7s. Or 4 nested groups with 5 layers, it is faster by 3.5s. It depends on how many layers you have and how many task in each layer.
We do use a lot of nested groups so this would be an improvement.

[uranusjr]

This looks reasonable to me and should be OK to be merged. One more potential path to optimise things though; feel free to investigate in another PR.

[MarosMK]

@uranusjr, thanks for approving.

Any expected timeline for merging this and including it in a new release?

[uranusjr]

You just broke the PR…

[eladkal]

You just broke the PR…

it's a rebase done from the Ui while github had a bug https://github.com/orgs/community/discussions/51948
They reported that closing and opening the PR will fix the problem.. lets see

[boring-cyborg]

Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions.