Feature suggestion: ability to interactively disable deployment of selected resources #19

When developing a template, it may sometimes be necessary to delete a resource(s) in order to update the configuration (e.g. if using fixed names, or when migrating from an API Gateway w/ Target to explicitly configured stages). In these situations, what seems to be the only two recourses are:

1. Delete the entire template and redeploy it. This is fine and straightforward but impacts many more resources than strictly necessary, which could be disruptive or at least slows down iteration.
2. Selectively comment out the affected resources and anything that depends on them. Manually commenting in/out resources is tedious enough, but it's also fairly error-prone when dealing with resource dependencies.

This feature suggestion is to make option 2. more convenient. We can parse the template and resolve resource dependencies, then given some flag to apply-stack present a checklist to the user to interactively disable some resources. Disabling a resource would also disable any resources/outputs that depend on it. The disabled resources/outputs could then be filtered out of the template prior to deployment.