Preventing inconsistent range reads in etcd transactions

Problem

A transaction path could execute a range operation in a way that led to inconsistent data. The behavior needed a targeted correction and a changelog entry describing the fix.

Changes

I changed the apply path to skip range execution in the affected transaction case, preventing the inconsistent result. I then added the corresponding changelog entry to record the correction for users.

Result

The transaction path no longer performs the range operation that caused the inconsistency, and the correction is documented in etcd release notes.

Commits: transaction fix, changelog entry