fix: add deterministic accrual replay tie-break

[pchieneye]

fix: add deterministic accrual replay tie-break

Summary

This change makes accrual replay ordering deterministic when multiple updates share the same period and amount.

What changed

• Added a canonical replay ordering for accrual updates based on:
  • period_id
  • amount
  • holder address as the final lexicographic tie-break
• Added a regression test covering same-period, same-amount ties across different holders.
• Documented the replay-ordering behavior in the accrual ledger docs.
• Aligned the storage-layout registry with the current DataKey2 enum variants so the build script remains consistent.

Why

Without a deterministic tie-break, replay ordering could vary when multiple accrual updates shared identical period and amount values. This change keeps replay stable for indexers and downstream consumers without changing the underlying accrual totals.

Testing

• Added regression coverage for the tie-break behavior in the accrual ledger tests.
• Verified the modified files are free of editor-reported Rust errors.

Closes: #603

[drips-wave]

@pchieneye Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits