Make robustness report and its log show consistent member-id

[nwnt]

What would you like to be added?

We recently added the member-id in #20932, but the ID shows up in operations.json report different than what's being logged. We should make them consistent by making the member-id in operations.json match with the log.

cc @serathius

Why is this needed?

For easier understanding the result from robustness tests.

[awhvish]

Hello @serathius , I would like to work on this issue as a new contributor, the instructions seems pretty straightforward

[serathius]

Sounds good.

[awhvish]

/assign

[serathius]

Looking for human contributor :P

[serathius]

/help

[awhvish]

That was not the goal of the PR. Based on response format I assume there was zero human involved.

Hi, it might seem so, but I just used it to create the text response for PR which I though was irrelavant for using AI
Please give me some time to have a look at it again, I might have misunderstood

but overall what I understood was in operations.json inside /tmp/TestRobustness[..] the MemberID shows in uint64 format, which did not match with the string response in etcd logs - or am I misunderstanding something?

there was another way to solve this by using JSONMarshal, but I wasnt sure it was the right way to handle this - and I was waiting for a feedback in the PR.

[slyt3]

@serathius can I work on this? as far as I know I am human haha

[PhantomInTheWire]

/assign