* - fix snafu with NOCASE (logic inverted)
- add IsReversed to simplify reversal logic

* PR ref

* - support ARINFO FULL
- refactors ArrayInfo initialization to be span based, and put the main logic inside ArrayInfo

technically this is a break, but: `[Experimental]`

* release notes

* SENTINEL: defensive check around ROLE

* PR number

* CI fail; try updating test-reporter

* bare bones INCREX first stab

* tidy INCREX impl

* add INCREX integration tests

* merge

* compensate for 8.8RC1 API and behaviour changes

* let's try adding the new files

* oops, make sure flags is the final arg

* account for last-minute-changes to INCREX

* add my expectation assertions as integration tests; multiple failures - I'm asking "server" for guidance

* update CI image

* update test expectations to implement the reality of the server as-at 8.8

* update CI image to 8.8

Propagate exceptions out of Message.WriteTo so PhysicalBridge's outer
write path can record a connection failure, and have HandleWriteException
kill the PhysicalConnection via RecordConnectionFailed.

Without this, a write that throws partway through a frame (e.g. an OOM
during serialization) leaves bytes on the wire while the response queue
still considers the slot healthy. The next reply from the server then
matches against the wrong in-flight message — the symptom seen in #2883,
#2804, and #2919, where commands return values intended for a different
caller. HighIntegrity mode mitigates the symptom by detecting the desync
after the fact via per-message echo checksums; this change addresses the
underlying cause for the write-side variant.

Adds three tests:
 - WriteTo must rethrow non-RedisCommandException out of WriteImpl, so
   the outer bridge catch can act on it.
 - RedisCommandException continues to surface unwrapped (it carries its
   own meaning and is excluded from the WriteTo catch filter).
 - End-to-end: a Message whose WriteImpl throws faults the awaiter with
   a RedisConnectionException(InternalFailure) AND raises a
   ConnectionFailed event, proving the physical connection was torn down.

* investigation into socket failure

* 1. make TCP keep-alives an explicit option (default: "on")
2. hard-disable TCP keep-alives on DNS endpoints for non-Windows before .NET 10

* release notes

* update CI image to 8.8

* fix typo in runtime test isolation / port selection.

* Add OptionKeysAreAllNormalized to ensure all keys are correctly normalized; add tcpKeepAlive to docs

* stabilize DeleteLastElementPublishesArrayDeleteBeforeKeyDeleteNotifications

* allow more grace while waiting for ArrayTests work; only run that test in DEBUG

* reduce CI brittleness by restricting tests that have wide side-effects; they can't run in parallel between runtimes

* more CI stabilization; HOTKEYS this time