Handle fork deadline boundaries and transaction-cancel edge cases in fork/auction/reporting flows

[KillariDev]

Summary

• Added inclusive/exclusive fork-window boundary coverage for migrations and auction transitions (Peripherals Solidity tests), ensuring operations are still allowed at exact deadlines and correctly rejected one second later.
• Added regression coverage for liquidation + claim interactions so finalized auction proceeds remain claimable by the original bidder after partial vault liquidation.
• Exposed additional auction/helper utilities through test fixtures to support new edge-case scenarios and mixed settlement flows.
• Updated reporting timing logic to use a unified hasReportingOpened check in UI stages and controls, aligning button states with protocol reporting-open semantics.
• Extended transaction tray and operation hooks to support explicit transaction-cancel state transitions used by reporting and oracle-related flows.
• Strengthened multiple frontend hooks and contract-layer helpers (deployment, fork auction, market reporting, oracle, vault, trading) to align with the new edge-case behavior.

Testing

• Not run (no command execution performed in this session).