currently we just update the state of pipeline in crates/pipeline-manager/src/runner/pipeline_automata.rs ( whenever we transit to some state ) using set_deployment_status from crates/pipeline-manager/src/db/operations/pipeline.rs

for debugging purposes, it would be better to have a pipeline_lifecycle_history ( use better & appropriate name here ) in crates/pipeline-manager/migrations/V0__ddl_base.sql which is later used to keep track of state in deployment status?

ideally, we want to track the additional info in the table, e.g. for stopped state, we can add in the error message to determine why it was stopped.