Implement contract dependency resolution and version management

[Just-Bamford]

Description

Problem

Sorokit currently lacks a consistent way to model dependencies between Soroban contracts. Applications integrating multiple contracts must manually track required contract versions and can encounter runtime failures when a dependency changes or becomes incompatible.

Solution

Introduce a contract dependency resolver that builds a dependency graph from contract metadata, tracks required versions, and validates compatibility before a contract is used. The resolver should detect conflicting version requirements and expose enough context for callers to understand which dependency caused the conflict.

Support cached dependency metadata and explicit refresh so applications can avoid unnecessary network requests while still detecting upgrades.

Acceptance Criteria

• Contract dependencies can be registered and represented as a dependency graph
• Dependency versions are tracked and validated against required constraints
• Conflicting or incompatible versions return a structured Sorokit error
• Nested/transitive dependencies are resolved correctly
• Dependency metadata supports configurable caching and refresh
• Resolution does not enter infinite loops when circular dependencies exist
• Tests cover direct, nested, conflicting, circular, and missing dependencies
• Public APIs are exported through src/soroban/index.ts and src/index.ts

Note for Contributors

Review the existing Soroban contract metadata and client patterns before introducing new abstractions. Keep dependency resolution separate from contract invocation so existing callers remain backward compatible. Include tests for both successful resolution and failure paths.

[Gozirimdev]

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

please can I work on this

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

[dakwa001]

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

Hi! I’d like to take this issue. I’ll go through the existing implementation, identify the root cause, and work on a clean solution before submitting a PR for review.

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

[drips-wave]

Congratulations, @dakwa001! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @dakwa001: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊