Custom CloudFormation resources should gracefully handle stack creation rollbacks

[rbalman]

Is your feature request related to a problem? Please describe.
Whenever a lambda backed custom resource creation fails, "github.com/aws/aws-lambda-go/cfn" returns a physicalResourceID to CloudFormation which doesn't exist. Then when CloudFormation tries to DELETE non-existent resource it fails. I have to manually skip the deletion of that particular custom resource to delete the Stack.

Describe the solution you'd like
Custom CloudFormation Resource should be able to be deleted like other normal Resources even though the CREATE event was not successful

Additional context

####### Here My Custom Resource is returning some ID when failed to create

####### Here AWS Security Group returning nothing when failed to create

Related PR

remind101/empire#918

[leepa]

See #107 as that's why it was added. I didn't add it originally because of this though - removing it again or at least reverting #108 might be the sensible thing here.

[bmoffatt]

reverting #108 makes sense to me. We'll have to re-open #107 to solve the error-masking problem originally described there.