[Advancement] Add multi-contract deployment graph planner

[Nanle-code]

Objective

Plan and execute multi-contract deployments respecting dependency order and shared init parameters.

Target area

deploy orchestrator utilities

Context

Real apps deploy multiple contracts; manual ordering is error-prone.

Requirements

• Accept a deployment manifest describing dependencies
• Dry-run prints ordered plan and estimated costs
• Fail fast on cycles or missing artifacts

Acceptance criteria

• Planner produces deterministic order for a sample graph
• Cycle detection is tested
• Docs include a multi-contract example

Pull request merge requirements

Pull requests that resolve this issue must not be merged until all of the following are true:

1. All required CI checks are green on the latest commit of the PR (build, tests, lint/format, and any workflow jobs required by branch protection).
2. The branch has no merge conflicts with the target branch (master / default), and a clean merge or rebase is possible without unresolved conflicts.
3. Review feedback is addressed, and the change remains focused on this issue’s acceptance criteria.

Contributors should run the local CI-equivalent checks before opening or updating the PR (see CI_ENFORCEMENT.md and CONTRIBUTING.md).

[sladeoj]

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

hello maintainer can i work on this issue please

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