Adding `IgnoreNotFound` Option while Deleting Resource/Stack

### Name of the resource

ALL

### Resource name

ALL

### Description

I wish I have the ability to ignore NotFound exception while deleting stack so it proceeds with deleting other resources that not deleted yet and ignore resources that deleted before by previous run/manually via AWS management console.

Such feature will ease cleaning process after failed deployment.

I am looking forward to have such option on resource/whole stack level.

Start by reviewing the requested behavior for deleting resources or a whole stack through AWS CloudFormation, including resources removed by an earlier run or manually in the AWS Management Console. Done means an agreed resource-level or stack-level option allows deletion to continue past NotFound errors while still removing remaining resources.

Written by the indexing model from the issue text.