Backport of [NET-3865] [Supportability] Additional Information in the output of 'consul operator raft list-peers' into release/1.16.x

[hc-github-team-consul-core]

Backport

This PR is auto-generated from #17582 to be assessed for backporting due to the inclusion of the label backport/1.16.

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@absolutelightning
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.

merge conflict error: unable to process merge commit: "13903531eacb25fca9a599a0cdd4f70d47e5f006", automatic backport requires rebase workflow

The below text is copied from the body of the original PR.

---

Description

As per requirement of NET - 3865, We want to have the 'commit_index' to be included in the output of 'consul operator raft list-peers -detailed'. This feature specifically useful in the cases where Consul is being upgraded to determine the replication rate and intervene as needed.

I have implemented it by calling a API /v1/operator/autopilot/health, storing the response in a map -> [server id, OperatorHealthReply]. Then this data is used to print the Commit Index by matching the id of server from this to server id in RaftGetConfiguration.

Testing

Create a consul cluster by following this tutorial.
kubectl exec -it consul-server-0 -n consul -- /bin/sh in one terminal
kubectl exec -it consul-server-1 -n consul -- /bin/sh in other terminal
do a ps and kill consul agent in the second terminal.
Run command consul operator raft list-peers

• execute the following command when agent is running
• consul operator raft list-peers
• Output -

PR Checklist

• updated test coverage
• external facing docs updated
• appropriate backport labels added
• not a security concern

---

Overview of commits

• 2f94024 - 7626d09 - 79aabc9 - 44eee41 - 1390353 - d118518 - d46a074 - 539dbc7 - 604b616 - 3a63b3d - 008946c - 509062e - cf22ea5 - eb69358 - 5c2a587 - 8e1f728 - 360ab9e - dc25344 - c461f59 - 3631708 - 5d479e8 - 40dc1e1 - e7afa34 - 8c1bab4 - 6b76d59 - c001e59 - 64e3b0a - 7f8d9d8 - fdad3bb - 1adcb15

[github-team-consul-core-pr-approver]

Auto approved Consul Bot automated PR

[david-yu]

@absolutelightning We should merge this PR into 1.16.x after GA since code freeze happened yesterday.

[david-yu]

@absolutelightning Could you check that all the commits went into this PR? Feel free to merge as this won't affect the 1.16.0 GA if we merge to release/1.16.x

[absolutelightning]

@david-yu Resolved