fix(ssubscribe): [cherrypick from v4] Force slots refresh on MOVED error when using ssubscribe

[htemelski-redis]

When issuing a ssubscribe command, the Cluster client creates a "regular" Redis client to establish a connection to the correct shard. This doesn't work if there's a failover since the client doesn't know how to correctly handle a MOVED response. This PR handles such events by propagating the ssubscribe MOVED error from the DataHandler, through the ClusterSubscriber and the ClusterSubscriberGroup to the RedisCluster client and forces slots refresh.

Direct port from #1987

[nkaradzhov]

CLGTM

[coveralls]

Pull Request Test Coverage Report for Build 17939972268

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 2 unchanged lines in 1 file lost coverage.
• Overall coverage decreased (-0.05%) to 90.681%

---

Files with Coverage Reduction	New Missed Lines	%
lib/connectors/StandaloneConnector.ts	2	94.64%

Totals
Change from base Build 17939975139:	-0.05%
Covered Lines:	2330
Relevant Lines:	2502

---

💛 - Coveralls