fix(types/address): correct sort comparator in Compose to satisfy strict weak ordering

[songgaoye]

Description

The Compose function used <= 0 in its sort comparator, which violates the
strict weak ordering requirement of sort.Interface. When comparing equal
elements, both less(i,j) and less(j,i) would return true, violating the
antisymmetry property.

Closes: #XXXX

[aljo242]

@songgaoye is there a test we can include to validate this behavior and can we add a changelog entry?

[songgaoye]

This unit test requires adding a lessBytes helper function @aljo242 in commit 09119d2.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 64.83%. Comparing base (d9bd545) to head (bd89e6f).

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #25944      +/-   ##
==========================================
- Coverage   64.86%   64.83%   -0.03%     
==========================================
  Files         890      874      -16     
  Lines       58581    57601     -980     
==========================================
- Hits        37997    37346     -651     
+ Misses      20584    20255     -329     

Files with missing lines	Coverage Δ
types/address/hash.go	100.00% <100.00%> (ø)

... and 21 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[aljo242]

Could we add tests for the Compose function itself?