Always print the raft_term in decimal

[ahrtr]

Fix 13709

When executing command etcdctl member list --hex -w json, it gets the cluster_id and member_id included in double quotes, but the raft_term isn't. All of three fields are uint64, so we should be consistent on displaying them.

Without this fix, the output can't be formatted using tool like jq either.

It's just a minor fix.

cc @serathius @spzala @ptabor

EDIT: I did some archaeology, the change was original introduced in PR/11812 in order to fix issues/9975. The original PR was just trying to resolve the inconsistent memberID output. But somehow it also printed the raft_term in hexdecimal. It seems not correct, because it can't be parsed correctly by json.NewDecoder, neither the tool something like jq, because the raft_term isn't a valid integer.

We have two solutions:

1. Always print raft_term in decimal, so that it works for both json.NewDecoder/json.Unmarshal and tool like jq;
2. Get the raft_term included in double quotes.

This PR follows the first solution. cc @tangcong @danbeaulieu @omkensey

[codecov-commenter]

Codecov Report

Merging #13711 (02872ae) into main (e814f6f) will decrease coverage by 0.24%.
The diff coverage is 100.00%.

❗ Current head 02872ae differs from pull request most recent head 4158323. Consider uploading reports for the commit 4158323 to get more accurate results

@@            Coverage Diff             @@
##             main   #13711      +/-   ##
==========================================
- Coverage   72.85%   72.61%   -0.25%     
==========================================
  Files         465      465              
  Lines       37880    37880              
==========================================
- Hits        27599    27508      -91     
- Misses       8508     8582      +74     
- Partials     1773     1790      +17     

Flag	Coverage Δ
all	72.61% <100.00%> (-0.25%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
etcdctl/ctlv3/command/printer_json.go	77.35% <100.00%> (ø)
client/v3/txn.go	73.33% <0.00%> (-26.67%)	⬇️
server/proxy/grpcproxy/register.go	69.76% <0.00%> (-9.31%)	⬇️
server/auth/simple_token.go	80.00% <0.00%> (-8.47%)	⬇️
client/pkg/v3/tlsutil/tlsutil.go	83.33% <0.00%> (-8.34%)	⬇️
client/v3/leasing/util.go	91.66% <0.00%> (-6.67%)	⬇️
etcdctl/ctlv3/command/lease_command.go	65.34% <0.00%> (-5.95%)	⬇️
server/etcdserver/api/rafthttp/msgappv2_codec.go	67.82% <0.00%> (-5.22%)	⬇️
server/storage/mvcc/watchable_store.go	85.14% <0.00%> (-3.99%)	⬇️
client/v3/leasing/cache.go	87.77% <0.00%> (-3.89%)	⬇️
... and 12 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e814f6f...4158323. Read the comment docs.

[ahrtr]

Just rebased this PR.

[ahrtr]

All tests passed, Please take a look. @serathius @spzala @ptabor

[ptabor]

Thank you. Please resolve the conflicts.

[ptabor]

Agree that raft_term as decimal is better choice. It's identifier that you might want to compare with </> other... while the hex is optically perceived as a unique identifier.

[serathius]

LGTM, please resolve the conflict.

[ahrtr]

Just rebased this PR. PTAL @serathius @ptabor @spzala Thanks.