Add BoundCondition fn to support bounded trace

[krebernisak]

• Add BoundCondition fn to support bounded trace
• Implement and integrate a simple BoundCondition that adds default boundaries for non-critical CCIP/MCMS msgs/opcodes (e.g., AC fwd notifications, CCIPReceive, etc) - Add DefaultTraceStopCondition impl

Supports smartcontractkit/mcms#615

[github-actions]

👋 krebernisak, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!

[Copilot]

Pull request overview

This PR introduces a BoundCondition function type to enable bounded trace analysis of TON blockchain messages. The enhancement allows users to define custom stopping criteria when traversing message traces, providing more control over trace depth and scope.

Changes:

• Added BoundCondition type and NoBound default implementation for trace boundary control
• Introduced TraceExitCodeWith and TraceSucceededWith methods that accept boundary conditions
• Refactored existing TraceExitCode and TraceSucceeded methods to use the new bounded variants with NoBound as default

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated 10 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.