The ECS Blue/Green Create Service step should dynamically evaluate whether the green ECS service already exists and create it when absent or update it when present, rather than requiring customers to figure this out themselves.

While planning a blue/green traffic shift template, we noticed the ECS Blue/Green Create Service step exposes a toggle for updating the green service. To run blue/green pipelines consistently across hundreds of ECS services without toil or bespoke scripting, the step needs to create the green service if it does not exist and update it if it does.

It seems odd that Harness will manage the ECS service's config, but needs customer intervention to understand whether to create the service or not. Allowing this to be automatically managed by the step will benefit all customers using ECS deployments in Harness