All stacks not automatically deleted

[PaulDuvall]

Now that we're using nested CloudFormation stacks for most of Dromedary, we no longer need to use many of the shell scripts that we're being used to manage stack creation/deletion - for the most part. This means we're no longer needing to use:

1. bootstrap-all.sh
2. cfn-bootstrap.sh
3. cfn-create-eni.sh
4. cfn-create-jenkins.sh
5. cfn-delete-all-appstacks.sh
6. cfn-delete-eni.sh
7. cfn-delete-stacks.sh
8. cfn-wait-for-stack.sh
9. codepipeline-create.sh
10. codepipeline-delete.sh
11. configure-jenkins.sh
12. delete-all.sh
13. pipeline-store.sh
14. test-jenkins-config.sh

We are still using the following scripts:

1. cfn-create-app.sh
2. eni-attach-to-app.sh
3. eni-detach.sh
4. packer-create-ami.sh
5. .sh scripts located at pipeline/jobs/scripts

The problem is that the Dromedary application stack pipeline/cfn/app-instance.json is launched from bin/cfn-create-app.sh through Jenkins via pipeline/jobs/scripts/drom-create-env.sh and, therefore, is not part of the master stack which means it doesn't get deleted and this means that resources such as VPC and ENI cannot be deleted even though they are part of the atomic Dromedary stacks.