Sync Odoo runtime env before deploy

[shiny-code-bot]

Summary

• sync DB-resolved runtime environment values into Dokploy before Odoo artifact ships
• keep raw Compose evidence redacted while verifying Dokploy persisted runtime env keys
• update explicit Odoo prod rollback to re-render raw Compose and sync runtime env instead of only changing DOCKER_IMAGE_REFERENCE

Verification

• python3 -m py_compile control_plane/cli.py control_plane/workflows/odoo_prod_rollback.py
• uv run python -m unittest tests.test_promote.ArtifactImageOverrideTests tests.test_odoo_prod_rollback
• uv run python -m unittest discover -s tests
• uv run ruff check --diff control_plane/cli.py control_plane/workflows/odoo_prod_rollback.py tests/test_promote.py tests/test_odoo_prod_rollback.py
• uv run ruff check control_plane/cli.py control_plane/workflows/odoo_prod_rollback.py tests/test_promote.py tests/test_odoo_prod_rollback.py

Notes

This keeps settings DB-backed: ship and rollback now resolve Launchplane runtime-environment records and managed-secret overlays, then push the resolved target env into Dokploy as executor input.