provider/aws: Treat INACTIVE ECS cluster as deleted

[radeksimko]

Either Amazon has changed this behaviour/timeouts or this just slipped through for some reason.

The PR is fixing the following acceptance test failure:

=== RUN   TestAccAWSEcsCluster_basic
--- FAIL: TestAccAWSEcsCluster_basic (8.43s)
    testing.go:165: Error destroying resource! WARNING: Dangling resources
        may exist. The full state and error is shown below.

        Error: Check failed: ECS cluster still exists:
        []*ecs.Cluster{{
          ActiveServicesCount: 0,
          ClusterArn: "arn:aws:ecs:us-west-2:212346748836:cluster/red-grapes",
          ClusterName: "red-grapes",
          PendingTasksCount: 0,
          RegisteredContainerInstancesCount: 0,
          RunningTasksCount: 0,
          Status: "INACTIVE"
        }}

        State: <no state>

[phinze]

@radeksimko we recently found that the DestroyCheck portion of the AccTest suite has not been called correctly for some time, so these errors will probably flush themselves out over the next few weeks.

This LGTM!

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.