[Advancement] Add contract size budget and section breakdown reporting

[Nanle-code]

Objective

Report WASM size budgets with section breakdowns to guide optimization before deploy.

Target area

optimize/gas/deploy preflight

Context

Size limits and fees make section-level insight actionable for developers.

Requirements

• Break down code/data/custom sections where possible
• Compare against configurable budgets
• Suggest next optimization commands

Acceptance criteria

• Report command outputs breakdown for fixtures
• Budget failures are clear and tested
• Docs link to optimization guide

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).

[Romeosin10]

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

Hello Maintainer, I’ve carefully looked through the issue and understand what is expected. I’m confident I can implement a solid solution and ensure the fix meets the project’s requirements. I’d be happy to take this issue on and work toward submitting a clean and well-tested solution.

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