`check_status_count_consistency` (unbounded scan) is completely unreachable

[dinahmaccodes]

Tier: Easy
Description: Unlike its paginated sibling check_status_count_consistency_range (used internally), the public unbounded check_status_count_consistency (consistency.rs:248-251) has zero callers anywhere, including tests.
Files: contracts/shipment/src/consistency.rs:248-251
Tasks:

• Either wire this function in behind appropriate limits/admin gating, or remove it in favor of the paginated variant
  Acceptance Criteria:
• No unreachable public consistency-check function remains

[Classictowo]

@Classictowo has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I’m Classictowo, a software developer with experience in Rust, smart contracts, and backend systems. I’d like to take this on because removing or properly wiring an unreachable public function will improve contract safety and maintainability. I can assess the existing consistency-check flow, preserve the paginated approach, and ensure the final implementation has appropriate tests and no unintended behavior changes.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Classictowo to this issue.