Add a few more predis integration tests with different connection types

[ajessu]

Description

Closes #315 (original issue) .
Closes #479 (attempted fix, which was already fixed by #574)

This was previously fixed by #574. As I explored #315 and the fix, noticed the current fix leaves out a few rarely used connection types without host and port tags information, as they do not use the AbstractConnection, while still being single node configurations.
Not the end of the world, but fix was simple.

Also added tests for many other connection types that do not need extra integrations (live connections into a Redis instance) to initialize.

---

More detail:

This moves from checking on extending the abstract class, into checking on implementing thise single node connection interface. All but one one core connection (Webdis) uses the interface without extending the abstract class. Any custom connection a user can define could also fall under this, though this is again, a rare case.

This change focused on the original intent of #574. Avoids trying to get a connection's host and port from a Redis cluster, since these cluster might have more than one connections configured. These connection types all implement the AggregateConnectionInterface.

On the other hand, single server connections implement the NodeConnectionInterface, which is also implemented by the AbstractConnection.

The NodeConnectionInterface guarantees the getParameter method, which returns a ParameterInterface implementing object, which in turn guarantees for any getter methods that:

• at least an string empty value for the host and port value, if they don't exist.
• the actual host and port configured for the Redis node.

See:
https://github.com/nrk/predis/blob/v1.1/src/Connection/ParametersInterface.php#L21-L32
and
https://github.com/nrk/predis/blob/v1.1/src/Connection/Parameters.php#L146-L151

Readiness checklist

• (only for Members) Changelog has been added to the appropriate release draft. Create one if necessary.
• Tests added for this feature/bug.

Reviewer checklist

• Appropriate labels assigned.
• Milestone is set.
• Changelog has been added to the appropriate release draft. For community contributors the reviewer is in charge of this task.

[krakjoe]

I'm going to close this as it would appear to be stale (as well as at least partly inapplicable).

If I'm wrong to do that, please open a new PR, and accept my apologies in advance.

[bwoebi]

Reference: #1094 fixed this as well.