Deregistering versions is not intuitive

I hit the maximum number of versions of my resource and it wasn't clear what I should do.

* Am I stuck?
* Can I delete old types?
* Can I update a resource without incrementing the version (useful when developing)?

I eventually figured out that I needed to deregister old versions, but that feature is nested within the deregister-type command and it took longer than I would have liked to figure out I can use that to deregister individual versions of a type.

I'd like to be able to say "deregister-version" and give it an arn to deregister

I'd like to be able to say "deregister-non-default" and give it a type and it will deregister all non-default versions for that type (though I can see how this might be dangerous)