Remove memberID from data corruption alarm

[ahrtr]

What happened?

Only leader performs the corruption check, and it always assumes that it's one of the followers' data corrupted. It isn't correct, it's also possible that the leader data corrupted.

Please refer the discussion in #14828

What did you expect to happen?

Remove memberID from data corruption alarm or set it as 0.

How can we reproduce it (as minimally and precisely as possible)?

Trigger a data corruption.

Anything else we need to know?

We only need to fix this for 3.5 and 3.4.

Etcd version (please run commands below)

$ etcd --version
# paste output here

$ etcdctl version
# paste output here

Etcd configuration (command line flags or environment variables)

paste your configuration here

Etcd debug information (please run commands blow, feel free to obfuscate the IP address or FQDN in the output)

$ etcdctl member list -w table
# paste output here

$ etcdctl --endpoints=<member list> endpoint status -w table
# paste output here

Relevant log output

No response

[ahrtr]

The easiest solution might be intentionally set the memberID as 0, otherwise we need to update the alarm structure. WDYT? @serathius

[serathius]

Sounds Good

[ahrtr]

Related to #14272

[serathius]

Note, can develop changes first on main branch?

[ahrtr]

Note, can develop changes first on main branch?

Only 3.4 and 3.5 need this change. main will follow #14828

[ahrtr]

Resolved.