Fix for #1347 (comment)

Trimmed the whitespace eclint complained about:
https://github.com/predis/predis/actions/runs/5967543294/job/16189493022?pr=1370#step:6:17

Test coverage?

Test added. You need to "Approve and run workflows" to trigger tests and get result from coveralls

Redis 7 errors unrelated (might have been introduced by last week update of Redis 7.2)

Can be verified with #1372

coverage: 78.183% (+0.02%) from 78.167% when pulling 5cb1702 on kylekatarnls:feature/setinfo-opt-out into 16bdd83 on predis:v2.x.

@tillkruss https://github.com/predis/predis/pull/1370/files#diff-7171e490ba29ca3a384a9f5d48189766b2f8c9f8af0371d523c8482770d65a0eR35

Isn't it clear enough?

No, why do we need client name/version to be configurable at all? It should always be Predis, no?

@tillkruss I believe @chayim knows more than me about that. It looks like clients should be able to advertise their own products this way. F.E if magento uses predis as Redis client, they can override this values, so cloud instances can collect this kind of data about magento clients.

The reason for allowing setting names and versions is to enable "whatever people want to create". It's entirely possible to build client solutions on top of existing clients (nredisstack and stackexchange.redis for example). This is the vision of how these things would be used.

It also allows (same example) for a client to advertise something like:
Name: Foo [predis]

Thus, sharing all.

@kylekatarnls: I'll merge a quick fix in #1399, because #1398 is making this more complicated.