Prefix each entry with a timestamp that looks like:

```
18:18:47.9261: Connecting (async) on .NET Core 3.1.16
18:18:47.9263: cachename.redis.cache.windows.net:6380/Interactive: Connecting...
18:18:47.9463: cachename.redis.cache.windows.net:6380: BeginConnectAsync
18:18:47.9483: 1 unique nodes specified
```

See #1371
and
#1246

Adding some new condition overloads for XLEN, useful for deleting empty streams in a safe method. It's a very simple change, one line to the length condition implementation plus the overloads.

Tests have been added and pass, though I don't have the infrastructure to run the failover/cluster/etc tests. I can include the .trx file if that's important.

I would have liked to add more conditions, like one that calls XPENDING to examine the number of pending messages, but that would need a new condition implementation with different messages and more complicated code to examine the results. Maybe I'll do it in another pull request, if I find the time.

Enables the use of extensions that customize ConfigurationOptions settings to tune behavior or add new capabilities. As proposed in #1801 

Adds:
- New overloads of the ConnectionMultiplexer.Connect() and ConnectAsync() methods, that take an additional Action parameter to customize the ConfigurationOptions
- A new ConfigurationOptions.Apply() method to apply the same type of customizer directly to a ConfigurationOptions instance, before connecting

Co-authored-by: Nick Craver <craver@stackoverflow.com>

* add As to fields

* add On Json API to client

* add fieldName class

* API

* syntax

* test json index definition (ON JSON)

* test create with fields name (as)

* test return with field names (return as)

* remove redundant using

* Update FieldName.cs

This prevents a disposal race from killing us in connection phases and such, protected against in the counters above in Unofficial (see https://github.com/mgravell/Pipelines.Sockets.Unofficial/blob/19b141f30fe2485dd79993be0ac87a9fc6b34b74/src/Pipelines.Sockets.Unofficial/SocketConnection.cs#L235) but not here - adding the same protection guard.

Stack trace of such an error:
```
----- Inner Stack Trace -----
   at System.Runtime.InteropServices.SafeHandle.DangerousAddRef(Boolean& success)
   at System.StubHelpers.StubHelpers.SafeHandleAddRef(SafeHandle pHandle, Boolean& success)
   at Interop.Winsock.ioctlsocket(SafeSocketHandle socketHandle, Int32 cmd, Int32& argp)
   at System.Net.Sockets.SocketPal.GetAvailable(SafeSocketHandle handle, Int32& available)
   at System.Net.Sockets.Socket.get_Available()
   at StackExchange.Redis.PhysicalConnection.GetSocketBytes(Int64& readCount, Int64& writeCount) in /_/src/StackExchange.Redis/PhysicalConnection.cs:line 1250
   at StackExchange.Redis.PhysicalBridge.GetOutstandingCount(Int32& inst, Int32& qs, Int64& in, Int32& qu, Boolean& aw, Int64& toRead, Int64& toWrite, BacklogStatus& bs, ReadStatus& rs, WriteStatus& ws) in /_/src/StackExchange.Redis/PhysicalBridge.cs:line 304
   at StackExchange.Redis.ConnectionMultiplexer.ReconfigureAsync(Boolean first, Boolean reconfigureAll, LogProxy log, EndPoint blame, String cause, Boolean publishReconfigure, CommandFlags publishReconfigureFlags) in /_/src/StackExchange.Redis/ConnectionMultiplexer.cs:line 1748
```

* fox .ctor breal (avoid MME)
fix "filed" typo (except for .ctor break)

* update release notes

Part of #1847, giving better debug information when this happens.

…processor (#1854)

Pain point in the last release was a spiral of death triggered (or at least: exacerbated) by the backlog processor

Fixing comments

* Adding sortable tag field support

* UNF

* move unf to base class

* Check that UNF can't be given to non-sortable filed

* Check that UNF can't be given to non-sortable filed

* enforcing correct ordering of UNF & Sortable options

* incorporating Marc's suggestions

Co-authored-by: AvitalFineRedis <avital.fine@redislabs.com>

Adds latest NRediSearch index APIs and fixes test suite against older modules.

Co-authored-by: Nick Craver <nrcraver@gmail.com>

…RightPop, and ListRightPopAsync (#1850)

Add support for count argument to ListLeftPop, ListLeftPopAsync, ListRightPop, and ListRightPopAsync

Optional Count argument was added in Redis 6.2

Co-authored-by: Nick Craver <nrcraver@gmail.com>

Fixes #1729

Co-authored-by: Nick Craver <nrcraver@gmail.com>

Adding an automatic subscription to the AzureRedisEvents pubsub channel for Azure caches. This channel notifies clients of upcoming maintenance and failover events.

By exposing these events, users will be able to know about maintenance ahead of time, and can implement their own logic (e.g. diverting traffic from the cache to another database for the duration of the maintenance event) in response, with the goal of minimizing downtime and disrupted connections. We also automatically refresh our view of the topology of the cluster in response to certain events.

Here are some of the possible notifications:

```
// Indicates that a maintenance event is scheduled. May be several minutes from now
NodeMaintenanceScheduled,

// This event gets fired ~20s before maintenance begins
NodeMaintenanceStarting,

// This event gets fired when maintenance is imminent (<5s)
NodeMaintenanceStart,

// Indicates that the node maintenance operation is over
NodeMaintenanceEnded,

// Indicates that a replica has been promoted to primary
NodeMaintenanceFailover
```

Co-authored-by: Michelle Soedal <ansoedal@microsoft.com>
Co-authored-by: Nick Craver <nrcraver@gmail.com>