Ensure K8s tests are completed before finalization

[jscheffl]

See #49825 (comment)

[jscheffl]

Ups, I assume there is mow not depending on "finalize" :-(

[potiuk]

Indeed. Actually that was quite deliberate... because k8s tests were generally slow and brittle, but they are much more stable now after separatlng them to individual jobs, so we should be able to bring back this dependnecy.

Sorry, need re-review :-D

[jscheffl]

@potiuk mhm, now I checked and also task sdk and airflowctl were independent of finalize. Either we need a general finalizer or... as now here in the PR all tests which were previously before Slack notification are dependency to finalize.... and Slack only depends on finalization... don't know if this is "good"?
...or we need a "final final check" which is required to auto-merge

[gopidesupavan]

@potiuk mhm, now I checked and also task sdk and airflowctl were independent of finalize. Either we need a general finalizer or... as now here in the PR all tests which were previously before Slack notification are dependency to finalize.... and Slack only depends on finalization... don't know if this is "good"? ...or we need a "final final check" which is required to auto-merge

Its fine i guess under one finalisation.

[github-actions]

Backport failed to create: v3-0-test. View the failure log Run details

Status	Branch	Result
❌	v3-0-test

You can attempt to backport this manually by running:

cherry_picker fcacd12 v3-0-test

This should apply the commit to the v3-0-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue