feat: Allow specifying sync steps in conjunction with recipes

[adamspofford-dfinity]

Currently you can either specify build: and sync: or a recipe. But while a build owns the WASM module end-to-end as part of a toolchain, syncing is part of the canister rather than the toolchain, so projects should be able to define sync steps without restructuring their configuration. This PR makes it so that you can add sync: even if you are already using a recipe.

_{Stack created with GitHub Stacks CLI • Give Feedback 💬}

[Copilot]

Pull request overview

Enables canisters using recipes to append custom sync steps after recipe-provided steps.

Changes:

• Extends recipe manifests and consolidation logic with optional sync steps.
• Updates schemas and documentation.
• Adds unit and CLI integration tests.

Reviewed changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
CHANGELOG.md	Records the feature.
crates/icp/src/manifest/canister.rs	Parses recipe sync configuration.
crates/icp/src/project.rs	Appends manifest sync steps after recipe steps.
crates/icp-cli/tests/recipe_tests.rs	Tests effective sync ordering.
docs/schemas/icp-yaml-schema.json	Updates project schema.
docs/schemas/canister-yaml-schema.json	Updates canister schema.
docs/reference/configuration.md	Documents configuration syntax.
docs/guides/using-recipes.md	Adds usage guidance.
docs/concepts/recipes.md	Clarifies recipe and sync semantics.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.