Rollout of new revision will kill old pods at the same time

[houshengbo]

What version of Knative?

1.16.1 or above
1.17.x
1.18.x
main branch

Expected Behavior

When we launch a new revision of the knative service, the pods of the old revisions should not be terminated, until all the minimum number of the pods for the new revision are up.

Actual Behavior

Old pods of the old revision starts to terminate when the new pods of the new revision are launching.

Steps to Reproduce the Problem

Create a knative service. Then create a new version of the same service.
Watch the changes of the pods or deployments for both of the revisions.

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[dprotaso]

Did a bisect - the bug was introduced in #15503