feat: Add support for new redis command CLIENT NO-TOUCH

[ktsivkov]

Issue: #2519

[ktsivkov]

@monkey92t hey, could you please review this one?

[monkey92t]

Based on my understanding, this is a client state, not a regular command. It labels a network connection, and we should figure out how to handle similar commands.

[ktsivkov]

@monkey92t @SoulPancake
Some brainstorming, based on my limited understanding we need to..

• be able to "tag" connections (multiple conn* handle pool and cluster?)
  i.e.

type baseClient struct {
	...
	connPool pool.Pooler // This here

• after executing (such labaling commands), we need to send all followup commands to this exact connection until they are disabled again
• find a way to handle connection drops (if a labeled connection is lost, we need to be able to handle it)

Needs some more thought but what comes to my mind on the fly is either one of those...

• We could use some kind of a Builder interface

// ClientNoTouch /or any other labeling command/ Creates and tags a new connection and returns it for use
cl := redis.ClientNoTouch()
cl.Get(...)
cl.Close()

• We could use sync.map to create a map of the connections and their labels, such as client no touch
• We could introduce / or re-use / a feature to group connections that are initiated with such pre-executed commands redis.CreateGroup(ctx, &GroupConfig{ClientNoTouch:true})