chore(ecs): add new enum values for ecs

[github-actions]

This PR updates the enum values for ecs.

[abidhasan-aws]

Doc for launchtype:
https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-resource-ecs-service.html#cfn-ecs-service-launchtype
https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-configuration.html

more on ECS managed instances: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ManagedInstances.html

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #35806 has been dequeued. The pull request rule doesn't match anymore. The following conditions don't match anymore:

• -label~=(blocked|do-not-merge|no-squash|two-approvers|priority-pr)
• check-success=build
• check-success=validate-pr
• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue default-squash]
    • -label~=(blocked|do-not-merge|no-squash|priority-pr)
    • check-success=build
    • check-success=validate-pr
    • any of: [🛡 GitHub branch protection]
      • check-neutral = validate-pr
      • check-skipped = validate-pr
      • check-success = validate-pr
    • any of: [🛡 GitHub branch protection]
      • check-neutral = build
      • check-skipped = build
      • check-success = build.

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[aemada-aws]

https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-resource-ecs-service.html#cfn-ecs-service-launchtype
The cfn resource does not support that value in launchType, when developing the feature it was mentioned that to use managed instances, it needs to be added as a capacity provider not as a service launch type. I will check with ECS team.

[abidhasan-aws]

PR has been updated to exclude the enum value "MANAGED_INSTANCES".

Reason for this exclusion:
Customers cannot pass launchType=MANAGED_INSTANCES and this value only appears in Describe calls. In order to use Amazon ECS Managed Instances, users must use capacityProviderStrategy request parameter and omit the launchType request parameter.

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.