fix(id): always compare legacy IDs below newly formatted IDs

[mnoah1]

Update stovepipe's ID comparisons - place all legacy requests before the new numerical only value. This will avoid existing queues getting wedged when they hit the boundary between the last legacy request, and first new one.

Why?

Without this change, queues would have stalled at the boundary between the last legacy request bookmark, and the next incoming request in the new format. The comparison would have continually failed, and never drained out, because we are trying to compare a request in the old format, with a request in the new format.

What?

Adjust the request ID comparator to place all legacy requests before new ones in ordering.

Within each format, IDs retain numeric ordering. Decimal IDs sort after all valid legacy IDs; this assumes a one-way writer switch from legacy to decimal IDs.

Test Plan

• Updated tests
• During deployment, monitor that new requests continue to advance beyond the last legacy-formatted request.
• ✅ Rebased the RFC → ID implementation → compatibility stack onto main (5b6af68f), preserving all eight commits and the compatibility patch's five-file scope.
• ✅ make lint, make check-gazelle, make check-mocks, make check-tidy, make build, and make test (130 targets passed)
• ✅ git diff --check
• ⚠️ aifx verify could not complete its monorepo coverage, generic Go lint, and UReview API checks; repository-native checks above passed.

Stack

1. docs: define scoped sequential resource IDs #762
2. feat(ids): use queue-scoped decimal resource IDs #770
3. @ fix(id): always compare legacy IDs below newly formatted IDs #778