[v2-10-test] Avoid grouping task instance stats by try_number for dynamic mapped tasks (#44300)

[github-actions]

(cherry picked from commit 5e52bd2)

Co-authored-by: Shahar Epstein 60007259+shahar1@users.noreply.github.com

[shahar1]

1. The unit test fails, I'll take care of it.
2. @potiuk What do you think that we should do with back-ported newsfragments?
   Should we keep them with the original PR id, or change it to the backport's? It could be automated as part of the cherry-picker, I wonder if it's worth the effort :)

Update: I just checked and it seems that we don't have many back-ported news fragments.

[potiuk]

Should we keep them with the original PR id, or change it to the backport's? It could be automated as part of the cherry-picker, I wonder if it's worth the effort :)

Should be original PR.

Update: I just checked and it seems that we don't have many back-ported news fragments.

Yes - they are deleted after they are incorporated by release manager in release notes for 2.10.1* when they are relased - this is part of towncrier workflow. We should also then delete the newsfragment from main I guess (@jedcunningham ? @ephraimbuddy @utkarsharma2 ) because otherwise the newsfragment will appear in two releases. I think it is automated by our workflow and one reason why newsfragments should be committed in their corresponding PR because "cherry-picking" PR means also "cherry-picking" release notes.

[potiuk]

So I am not sure if the rename was a good idea. :)

[shahar1]

Should we keep them with the original PR id, or change it to the backport's? It could be automated as part of the cherry-picker, I wonder if it's worth the effort :)

Should be original PR.

Update: I just checked and it seems that we don't have many back-ported news fragments.

Yes - they are deleted after they are incorporated by release manager in release notes for 2.10.1* when they are relased - this is part of towncrier workflow. We should also then delete the newsfragment from main I guess (@jedcunningham ? @ephraimbuddy @utkarsharma2 ) because otherwise the newsfragment will appear in two releases. I think it is automated by our workflow and one reason why newsfragments should be committed in their corresponding PR because "cherry-picking" PR means also "cherry-picking" release notes.

Thanks for the info :)

So I am not sure if the rename was a good idea. :)

Dropped last commit