Verify Odoo post-deploy override handoff

[cbusillo]

Summary

• Add redacted post-deploy override evidence to Odoo target-replacement results so testing deploys expose whether override records were found/rendered and whether website bootstrap was included.
• Validate required Odoo override env keys using the same effective docker exec environment array as the final data-workflow helper run.
• Treat inline workflow env overrides, including ODOO_INSTANCE_OVERRIDES_PAYLOAD_B64, as required for the generated schedule and emit a safe payload-present marker.

Verification

• uv run --extra dev ruff check control_plane/contracts/odoo_stable_target_replacement.py control_plane/workflows/odoo_stable_target_replacement.py control_plane/dokploy.py tests/test_odoo_stable_target_replacement.py tests/test_dokploy.py
• uv run python -m unittest tests.test_dokploy tests.test_odoo_stable_target_replacement

Live context

Devkit PR cbusillo/odoo-devkit#64 is merged and the cm_website testing artifact was republished as artifact-cm_website-6c29e37a24284c89. The deploy still failed canonical/logo while reporting post_deploy_status=pass, so this patch closes the Launchplane evidence gap and checks the final effective exec env before the helper runs.