refactor: Sorts retired amendments to reduce conflicts

[bthomee]

High Level Overview of Change

This change sorts the retire amendments.

Context of Change

We are on an amendment retiring spree, but each change results in conflicts because currently they all add the retired amendment to the end of the list. By sorting the list the number of conflicts should be reduced, making it easier to merge them.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Refactor (non-breaking change that only restructures code)
• Performance (increase or change in throughput and/or latency)
• Tests (you added tests for code that already exists, or your new feature included in this PR)
• Documentation update
• Chore (no impact to binary, e.g. .gitignore, formatting, dropping support for older tooling)
• Release

[pratikmankawde]

LGTM

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.3%. Comparing base (553fb5b) to head (fd40d18).
⚠️ Report is 1 commits behind head on develop.

Additional details and impacted files

@@            Coverage Diff            @@
##           develop   #5966     +/-   ##
=========================================
- Coverage     78.3%   78.3%   -0.0%     
=========================================
  Files          817     817             
  Lines        68965   68965             
  Branches      8301    8307      +6     
=========================================
- Hits         54021   54009     -12     
- Misses       14944   14956     +12     

see 3 files with indirect coverage changes

🚀 New features to boost your workflow:

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

[ximinez]

Should've added a note to add new items alphabetically. Maybe @pratikmankawde can do that on one of his pending retirement PRs?

[bthomee]

Should've added a note to add new items alphabetically. Maybe @pratikmankawde can do that on one of his pending retirement PRs?

I can add it when I merge one of his next PRs that are ready to merge but need conflict resolution in features.macro anyway.