feat: kratix add container should fail if people add multiple pipeline to delete step

[ChunyiLyu]

Context

We should stop people from adding multiple pipelines to promise delete and resource delete workflows. Kratix currently only supports multiple pipelines for the configure workflows.

Design

kratix add container resource/delete/pipeline2 ...
Error: multiple pipelines not allowed in delete workflows: found existing pipeline 'pipeline1'

[abangser]

Do you think we should stop this, or should we be supporting multiple pipelines in a delete workflow? I am not sure if we have discussed the use case for multiple pipelines in delete and the viability of running them.

[richcooper95]

At the moment, I think we should stop this ✋

We don't support it in Kratix (yet) and it's not come up as feedback. It'd take some work to implement multiple delete pipelines, so IMO it's better for the CLI to be consistent with the current state of Kratix, and change the CLI if/when we ever add the feature to Kratix!