v2.1.1

yolomover 2.1.1

Safety and correctness fixes for less-common disk layouts. The 2.1.0
happy path (512-byte sectors, 128-entry GPT, recovery after C:,
single-extent volumes) is unaffected; these harden the paths outside it.

- Volume locking actually engages now: FindFirstVolumeW names had a
  trailing backslash, so CreateFileW opened the filesystem root instead
  of the volume device and the lock/dismount pass silently did nothing.
- Fixed undefined behavior (misaligned VOLUME_DISK_EXTENTS cast) and a
  panic on multi-extent volumes (Extents[i] past the declared length).
- GPT entry array read/write/CRC are sized from the header's declared
  partition count rather than assuming 128 entries; entry size and count
  are validated before either header copy is written.
- Recovery partition's Windows number is recomputed from the on-disk
  layout after the move (the pre-move number was wrong when recovery sat
  before C:, which could re-register WinRE on the wrong partition).
- Storage stack is notified via IOCTL_DISK_UPDATE_PROPERTIES immediately
  after the GPT is committed.