Fix golangci revive error-strings issues

[ivanvc]

I was looking at the disabled linter rules and addressed the error-strings warnings. The only offending files are in the deprecated v2 client test code.

After speaking with @jmhbnz, he told me that @fuweid was working recently with the linter rules. So, it would be great if you could take a look at this.

Please read https://github.com/etcd-io/etcd/blob/main/CONTRIBUTING.md#contribution-flow.

[k8s-ci-robot]

Hi @ivanvc. Thanks for your PR.

I'm waiting for a etcd-io member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[jmhbnz]

/ok-to-test

[fuweid]

LGTM

[jmhbnz]

LGTM - Thanks @ivanvc

[ahrtr]

lgtm