…tel-0.x

Update module go.opentelemetry.io/otel to v0.15.0

…edis-v8-8.x

Update module go-redis/redis/v8 to v8.4.2

…tel-sdk-0.x

Update module go.opentelemetry.io/otel/sdk to v0.15.0

…a-1.x

Update module onsi/gomega to v1.10.4

The original text `all sentinels are unreachable` can sometimes be misleading, making some users think that all of their redis sentinels are down.

But it might not be the reality especially when using kubernetes and specify `c.sentinelAddrs` as the Service's domain. In this case, when the sentinel to which the domain is redirected runs into some errors despite other sentinels running healthily, the original text given by redis client will be confusing and delivering false message!

Just got out of a similar dilemma after checking the source code, feel free to correct me if I am wrong :)

make error message for unreachable sentinels more clear

Add support to get cluster replica node for a given key