[test] support cluster-api style rolling replacement upgrade

[ahrtr]

What would you like to be added?

Currently our e2e framework supports in-place upgrade. We just replace the binary, and reuse the existing data.

etcd/tests/framework/e2e/downgrade.go

Line 131 in 30452ab

func DowngradeUpgradeMembers(t *testing.T, lg *zap.Logger, clus *EtcdProcessCluster, numberOfMembersToChange int, downgradeEnabled bool, currentVersion, targetVersion *semver.Version) error {

However, the cluster-api/Kubeadm upgrades Kubernetes cluster in a rolling replacement approach,

• add a new learner first;
• promote it later
• remove an old node
• repeat the above steps until all nodes are replaced.

The key difference is the new member(learner) gets started without local data, so it may receive a snapshot from the leader.

We should update our e2e test framework to support both upgrade approaches,

• rolling in-place upgrade
• rolling replacement upgrade

Why is this needed?

To improve test coverage.

[ahrtr]

Link to:

• Learner promotion not being persisted into v3store may be propagated across multiple upgrades #20793
• [release-3.5] Fix Learner promotion not being persisted into v3store may be propagated across multiple upgrades #20797

[fuweid]

I handled that case in #19627. It's nice to have one option that it's to setup etcd member with specific release version.

[ahrtr]

I handled that case in #19627. It's nice to have one option that it's to setup etcd member with specific release version.

Please feel free to deliver a PR, thx