[Feature] Allow to turn off the default behavior of cosmos of creating task groups when a run & test are provided

[corsettigyg]

Description

Hello,

When dealing with cosmos, by default we will have the creation of a taskGroup with the name of the transformation and under it run and test while for tasks without tests, there is no taskGroup and only the {task}_run

It would be good to be possible to either make all of it flat (so no task groups) or by default always have a taskGroup and, in the absence of tests, just have run inside of it.

Use case/motivation

The reason is because when you try to extend cosmos and do some magic with it, the inconsistency in the task name makes it very hard to create a rule that will always work. For example, if an external DAG is referring to a cosmos DAG and we add a test to the dbt task we are poking, we would get an error in the external DAG since sensors are separated with . (so {taskGroupName}.run) while the current setup would still point to {task}_run.

Related issues

No response

Are you willing to submit a PR?

• Yes, I am willing to submit a PR!