feat: introduce recipes for development environments

[kacpersaw]

Summary

Introduce recipes to ocdev so users can define how a development environment is created from an existing snapshot, configured, and cleaned up.

Recipes contain reusable tasks and lifecycle hooks. Project files select a recipe and provide local configuration files and task defaults.

What was added

• YAML/JSON recipes with named tasks and ordered setup and cleanup hooks.
• Project definitions for copying local files, such as .env, into an environment.
• Commands to validate and register recipes, create environments, run tasks, and explicitly rerun setup.
• Environment inspection, operation history, and bounded task logs.
• Optional process-compose support for starting, stopping, restarting, and inspecting services.
• --json support across noninteractive management commands, preserving the existing list --json behavior.
• Documentation and Node/Redis and Python/PostgreSQL examples.

Behavior and safety

Each environment keeps the recipe version it was created with. Instance UUID checks, environment locks, and atomic port reservations protect lifecycle operations.

Failed setup leaves the container available for debugging. Cleanup hooks run before deletion and block it if they fail. Dry-run checks do not modify environments, but still require Incus.

Recipes execute trusted commands and require prepared snapshots. This PR does not add a build engine or manage the source snapshots.

Testing

• All 74 Nim unit and fake-Incus tests pass.
• Full rebuild and tests passed with a clean HOME and no Python or live Incus on PATH.
• CI passes; Atlas remains the dependency manager.
• Example definitions pass validation, but their application workflows have not been live-tested.

[pigmej]

lgtm