Improve update_service Command Functionality as Command Fails to Handle Non-Existent Services

[nanophate]

Orb version:

6.0.2

What happened:

Customer reached out about an issue when using our AWS ECS orb, particularly the update_service command https://circleci.com/developer/orbs/orb/circleci/aws-ecs#commands-update_service. When users use the update_service command and the service doesn't exist in AWS, the job keeps running for close to ~15 minutes and burns credits before failing.

Expected behavior:

Users should have the ability to pass a parameter to create the service if it doesn't exist already. Alternatively, if the service doesn't exist in AWS and customers don't pass a parameter, the job should fail immediately without burning any further credits.

Additionally, the orb should support the AWS CLI command for update-service https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/update-service.html, which includes a parameter to set the desired number of tasks (--desired-count) when updating a service. This would eliminate the need for customers to run additional jobs/steps as a workaround.