[pods] Finalize the replaced pods

[trasc]

What type of PR is this?

/kind feature

What this PR does / why we need it:

Finalize the Failed pods in a pod-group once a replacement pods are created.

Which issue(s) this PR fixes:

Fixes #1762

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Pod Integration: Finalize failed pods in a pod-group when replacement pods are created

[k8s-ci-robot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[trasc]

/test all

[netlify]

✅ Deploy Preview for kubernetes-sigs-kueue canceled.

Name	Link
🔨 Latest commit	e34470c
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-kueue/deploys/65e620d525aba300085720b9

[trasc]

/test all

[trasc]

/cc @alculquicondor

[alculquicondor]

nits just for future reference.

/lgtm
/approve
/cherry-pick release-0.6

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 6a6c6ac0a8df89aad7977fdcf5ea5a1d9557fe1e

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alculquicondor, trasc

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [alculquicondor]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[alculquicondor]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: d590e2f299bc666aef97cfee1f971269acecc338

[alculquicondor]

/cherry-pick release-0.6

[k8s-infra-cherrypick-robot]

@alculquicondor: once the present PR merges, I will cherry-pick it on top of release-0.6 in a new PR and assign it to you.

In response to this:

/cherry-pick release-0.6

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[alculquicondor]

Maybe the last attempt didn't catch the recently merged fix

/retest

[k8s-infra-cherrypick-robot]

@alculquicondor: #1766 failed to apply on top of branch "release-0.6":

Applying: Add Pick
Applying: Delete the replaced pods
Applying: KEP Update
Applying: Review Remarks
Using index info to reconstruct a base tree...
M	keps/976-plain-pods/README.md
M	pkg/controller/jobs/pod/pod_controller.go
M	test/e2e/singlecluster/pod_test.go
M	test/integration/controller/jobs/pod/pod_controller_test.go
Falling back to patching base and 3-way merge...
Auto-merging test/integration/controller/jobs/pod/pod_controller_test.go
Auto-merging test/e2e/singlecluster/pod_test.go
CONFLICT (content): Merge conflict in test/e2e/singlecluster/pod_test.go
Auto-merging pkg/controller/jobs/pod/pod_controller.go
Auto-merging keps/976-plain-pods/README.md
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0004 Review Remarks
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-0.6

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[alculquicondor]

@trasc please create a cherry-pick and highlight in the description any significant changes compared to this PR.

[alculquicondor]

/kind bug

[alculquicondor]

/release-note-edit

Pod Integration: Finalize failed pods in a pod-group when replacement pods are created