Track Odoo bootstrap provenance status

[cbusillo]

Summary

• add bootstrap-specific evidence on deployment records and inventory payloads
• expose bootstrap_run_status and readiness_status in Odoo stable bootstrap results
• keep current inventory deployment pointers unchanged on failed/partial bootstrap attempts while recording bootstrap_record_id
• document bootstrap execution vs public readiness semantics

Refs #557.
Stacked on #559.

Validation

• uv run python -m unittest tests.test_odoo_stable_bootstrap tests.test_filesystem_store tests.test_postgres_store
• uv run --extra dev ruff format control_plane/contracts/promotion_record.py control_plane/contracts/deployment_record.py control_plane/contracts/environment_inventory.py control_plane/workflows/inventory.py control_plane/workflows/ship.py control_plane/workflows/odoo_stable_bootstrap.py tests/test_odoo_stable_bootstrap.py
• uv run --extra dev ruff check .
• uv run --extra dev mypy control_plane tests
• uv run python -m unittest