test: simply the expected output for some curl test cases

[ahrtr]

Link to #16454

Random spaces may be inserted between fields in a marshalled json response in grpc-gateway v2, so simply the expected output to make it work for both v1 and v2.

[serathius]

This PR lowers quality of testing by skipping testing some fields, which we are no longer able to cover using a naive "find matching line" validation.

Could we just use json parsing for JSON API? For example create something like EtcdctlV3 that has spawnJsonCommand to parse JSON responses.

As we add more tests, the more complicated they are, and the more abstraction leak we get. Abstraction leak happens when abstractions you created doesn't correctly reflect the modeled problem. Like in those tests, we are using "find matching line" logic to analyse JSON responses, it doesn't work as JSON can have arbitrary whitespaces injected.

Until we fix our abstraction we will continue to need to patch our tests like in this PR.

[ahrtr]

This PR lowers quality of testing by skipping testing some fields, which we are no longer able to cover using a naive "find matching line" validation.

• Partially agree with this. Updated the verification on the response for /v3/kv/txn.
• For other verification, we only need to verify what the etcdserver returns. Use "/v3/election/resign" as an example, etcdserver just returns an ErrMissingLeaderKey, but gRPC adds some other info such as "code": 2. We only need to verify what the etceserver returns.
• Note that we are NOT testing the full functionalities. We just need to ensure the RESTful APIs are not broken when we upgrade grpc-gateway from v1 to v2.

[ahrtr]

Until we fix our abstraction we will continue to need to patch our tests like in this PR.

Pls do not make it big on this PR. If you have any additional thoughts, please raise a separate ticket to discuss; and anyone is welcome to refactor or improve existing test cases.

[jmhbnz]

Agree it would be best to more formally parse the json responses.

With that said, provided we have a follow-up issue created to track the work I am comfortable for it to be addressed at a later date.

[fuweid]

LGTM

[ahrtr]

thx all for the review!